Ez_b Namespace In New C++ Project

larschrjensen

Denmark

Asked Feb 2016 — Edited Feb 2016

Resolved by ptp!

I am having some trouble getting visual studio (vs2013) to recognize the EZ_B namespace in a new c++ project. It works fine in the Example Project from the SDK though. However, because of other components (specifcally YARP) I need to compile using CMake. My CMakeLists.txt looks like this:


CMAKE_MINIMUM_REQUIRED(VERSION 2.8.9)
SET(PROJECTNAME ez)
PROJECT(${PROJECTNAME})

find_package(YARP)
set(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} ${YARP_MODULE_PATH})

include_directories(${YARP_INCLUDE_DIRS})
add_executable(ez ez.cpp)
target_link_libraries(ez ${YARP_LIBRARIES})

So, can I include the EZ_B.dll already in cmake, and if not how can I add it to the solution that cmake generates?

Upgrade to ARC Pro

Discover the limitless potential of robot programming with Synthiam ARC Pro – where innovation and creativity meet seamlessly.

Compare Pro Features View Subscription Plans

ptp

PRO

USA

#1 Feb 2016

Lars,

In c++ world: To allow an executable to load/execute a DLL you need implicit (or explicit) link, for that you need to obtain a header file .h which contains the classes/declarations and you need a .LIB file which is used by the linker to create the call references between your code and the external lib.

there are cmake commands to specify the header and library location(s)

BUT you are not in c++ world, EZ_B is not a regular c++ library is a .NET managed library and can't be used as a regular library linked to plain c++ code.

what you have in ez.cpp is a c++/CLI extensions, which only visual studio can understand and compile, also you need to pass compiler directives to the visual studio.

In your cmake i don't see specific commands for the visual studio.

some examples:

clr compilation and exception management:


set_target_properties(${PROJECT_NAME} PROPERTIES COMPILE_FLAGS &quot;/clr /EHa&quot;)

to include .net references:


set_target_properties(${PROJECT_NAME} PROPERTIES VS_DOTNET_REFERENCES &quot;System;System.Core;WindowsBase;${CMAKE_CURRENT_SOURCE_DIR}/../3rdParty/EZ_B.dll;&quot;)

probably you will need more commands, but at least those two are missing.