zeex / cmake-modules

CMake modules for SA-MP plugin development

Name	Description
AddSAMPPlugin	Provides add_samp_plugin() function
AddSAMPPluginTest	Provides add_samp_plugin_test() function
AddSAMPPluginTestPR	Same as above but uses plugin-runner instead of samp-server-cli
AMXConfig	Defines platform-specific macros expected by AMX headers
FindPawnCC	Finds Pawn compiler executable
FindPluginRunner	Finds plugin-runner executable
FindSAMPSDK	Finds SA-MP plugin SDK
FindSAMPGDK	Finds GDK library and headers
FindSAMPServer	Finds SA-MP server executable
FindSAMPServerCLI	Finds samp-server-cli

cmake-modules's Issues

About 64bit plugins

Hi, recently we've been working to add 64bit support on open.mp. Plugins have to be recompiled, and I'm working on updating some popular plugins without fully porting them to the open.mp SDK since it would take too much time and open.mp has a perfectly serviceable SA-MP plugin loader.

However, when porting plugins to x64, this part of the CMake module gets in the way on compiling for 64bit:

cmake-modules/AddSAMPPlugin.cmake

Lines 6 to 9 in c0a8986

	if(CMAKE_COMPILER_IS_GNUCC OR CMAKE_CXX_COMPILER_ID MATCHES "Clang")
	set_property(TARGET ${name} APPEND_STRING PROPERTY COMPILE_FLAGS " -m32")
	set_property(TARGET ${name} APPEND_STRING PROPERTY LINK_FLAGS " -m32")
	endif()

Could there be a way to prevent this from being added to the build file? Generally speaking, most plugins already enforce -m32 on the whole project, so the addition of it on this file could be considered kind of superfluous. Removing that part entirely shouldn't be too much of an issue; it wouldn't break existing projects unless they actively update their submodules. Alternatively, you can add some kind of CMake variable to tell your module to not add -m32. Both would work in any case.