Am Donnerstag 16 April 2009 19:48:03 schrieb Mike Jackson:
> You will want to read this link
> <http://www.cmake.org/Wiki/BuildingWinDLL>
[...]
> PS: Feedback on that article is also welcome.

In OpenObex, we use additionally a .def file with exports. "obex.sym" is a list 
of symbol names (one per line) and is also used by libtool:

if ( MSVC )\r
  set ( OPENOBEX_DEF_FILE "${CMAKE_CURRENT_BINARY_DIR}/openobex.def" )
  file ( WRITE "${OPENOBEX_DEF_FILE}"
        "VERSION ${openobex_VERSION_MAJOR}.${openobex_VERSION_MINOR}\n"
       )
  file ( APPEND "${OPENOBEX_DEF_FILE}" "EXPORTS\n" )
  file ( READ "${CMAKE_CURRENT_SOURCE_DIR}/obex.sym" OPENOBEX_SYMBOLS )
  file ( APPEND "${OPENOBEX_DEF_FILE}" "${OPENOBEX_SYMBOLS}\n" )
endif ( MSVC )

You have to use this to get sensible symbol names that you can use from 
language bindings when using WINAPI.

OTOH, it should be sufficient to add a link to the right VisualStudio 
documentation. Almost everything regarding windows DLLs with msvc is described 
there, and lots better than what gcc provides as documentation (mostly 
cryptic).

HS

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to