I'm trying to utilize a custom library I've written across objects in a package I'm developing using Min, but have been generally unsuccessful so far. Apologies in advance for this lengthy post, but I'm pretty new to CMake and trying to wrap my head around what I need to do.

Let's say I have a "library" mylib, consisting of mylib.hpp and mylib.cpp, located at mypackagename/source/mylib/source. The mylib directory sits alongside min-api, min-lib and projects, and I've added it as a subdirectory to the package's CMakeLists.txt file.

After adding an #include "mylib.hpp" and code calling one of the methods to my object's .cpp file, I do the following in the object's CMakeLists.txt:

...
set(MYLIB_INCLUDE_DIR ${CMAKE_CURRENT_SOURCE_DIR}/../../mylib/source)
set(MYLIB_SOURCES_DIR ${CMAKE_CURRENT_SOURCE_DIR}/../../mylib/source)
file(GLOB MYLIB_SOURCES ${MYLIB_INCLUDE_DIR}/*.cpp)

#############################################################
# MAX EXTERNAL
#############################################################

include_directories( 
    "${C74_INCLUDES}"
)

set( SOURCE_FILES
    ${PROJECT_NAME}.cpp
)

add_library( 
    ${PROJECT_NAME} 
    MODULE
    ${SOURCE_FILES}
)
target_include_directories(${PROJECT_NAME} PUBLIC ${MYLIB_INCLUDE_DIR})
target_link_libraries(${PROJECT_NAME} LINK_PUBLIC ${MYLIB_SOURCES})
...

This doesn't work; the IDE (Xcode) and compiler can't find my header file. So I remove the target_include_directories line, and instead put ${MYLIB_INCLUDE_DIR} in the include_directories command, like so:

include_directories( 
    "${C74_INCLUDES}"
    "${MYLIB_INCLUDE_DIR}"
)

add_library( 
    ${PROJECT_NAME} 
    MODULE
    ${SOURCE_FILES}
)
target_link_libraries(${PROJECT_NAME} LINK_PUBLIC ${MYLIB_SOURCES})
...

I'm making progress, as my header file is found, but the object won't build, and I get an Apple Mach-O Linker (Id) Error, which, when digging it to it, essentially says symbol(s) not found for architecture x86_64.

I'm guessing that the target_link_libraries command isn't working as expected (target_include_directories and target_link_libraries work fine in my other, non-Min C++ projects), so I try to put my mylib sources directly into the ${PROJECT_NAME} target, by including them in the set(SOURCE_FILES ... command:

set( SOURCE_FILES
    ${PROJECT_NAME}.cpp
    ${MYLIB_SOURCES}
)

add_library( 
    ${PROJECT_NAME} 
    MODULE
    ${SOURCE_FILES}
)
...

This works, although this approach seems a bit kludge-y. The object builds, and works as expected in Max.

But if I now want to include Min/Max classes in my mylib library (I'd like to use atoms, for example), all hell breaks loose, so to speak. If I add #include "c74_min.h" to mylib.hpp, I get another Apple Mach-O Linker (Id) Error, which reports "duplicate symbols for architecture x86_64". If I omit "#include c74_min.h", the object won't compile as mylib can't access the c74::min namespace.

Am I missing something here, or is it not possible to include/link custom libraries with Min projects (while allowing those custom libraries access to the c74::min namespace)?

Any insight or help will be greatly appreciated; many thanks in advance.

include_directories( 
	"${C74_INCLUDES}"
)

add_library( 
	${PROJECT_NAME} 
	MODULE
	${SOURCE_FILES}
)
target_include_directories(${PROJECT_NAME} PUBLIC ${MYLIB_INCLUDE_DIR})
target_link_libraries(${PROJECT_NAME} LINK_PUBLIC ${MYLIB_SOURCES})
...

include_directories( 
	"${C74_INCLUDES}"
	"${MYLIB_INCLUDE_DIR}"
)

add_library( 
	${PROJECT_NAME} 
	MODULE
	${SOURCE_FILES}
)
target_link_libraries(${PROJECT_NAME} LINK_PUBLIC ${MYLIB_SOURCES})
...

set( SOURCE_FILES
	${PROJECT_NAME}.cpp
	${MYLIB_SOURCES}
)

add_library( 
	${PROJECT_NAME} 
	MODULE
	${SOURCE_FILES}
)
...

I'm trying to utilize a custom library I've written across objects in a package I'm developing using Min, but have been generally unsuccessf

problems-utilizing-a-custom-library-in-a-min-project

I'll try my best, but if I miss something (seems likely) please feel free to follow-up!

First, I'll start with an example that links against some libraries. 

This comes from our recently released Zero package in Max's Package Manager

. That example does some extra linking on Windows to a library that is already built (on the Mac the libraries are a part of the OS).

What makes that example easy is that the libraries are pre-built. One way that I've found myself tripped-up is because there can be a chicken-and-egg problem if your cmake file is supposed to build the file that it itself depends on, because it won't find the dependency until has been built and so it can't build it.

First, I'll start with an example that links against some libraries. This comes from our recently released Zero package in Max's Package Manager. That example does some extra linking on Windows to a library that is already built (on the Mac the libraries are a part of the OS).

What makes that example easy is that the libraries are pre-built. One way that I've found myself tripped-up is because there can be a chicken-and-egg problem if your cmake file is supposed to build the file that it itself depends on, because it won't find the dependency until has been built and so it can't build it.

Does this help?


Problems utilizing a custom library in a Min project