Intravision/reactos
1
0
Fork 0
mirror of https://github.com/reactos/reactos.git synced 2025-02-22 16:36:33 +00:00
Code Issues Projects Releases Packages Wiki Activity
reactos/dll/win32/framedyn/CMakeLists.txt

32 lines
802 B
Text
Raw Normal View History

[FRAMEDYN] Partplement framedyn.dll So far, only CHString class is implemented in it Regarding CHString class implementation: It has been implemented matching Windows behavior and bugs It might not be really nice at some points but this ensures compatibility with applications relying on it. As a side note: this might explain why this API was abandonned after w2k3... Regarding the DLL itself: Its implementation into ReactOS allows systeminfo.exe application from w2k3 to load and start initialization into ReactOS. It stops working later on with some IDispatch error. The DLL cannot be used to build any application against framedyn.dll with our "default" BE (read with G++). Only MSVC mangled name are exported so far (as on Windows ;-)) thanks to aliasing. This is why there are two spec files. This makes G++ unable to link with it though. This is the reason why there are no framedyn_apitests so far. Furthermore, the DLL only have exports for x86 and none for x64 for the moment. Any help is welcome for having exports for x64 target and to be able to have aliasing for G++ (from its mangled names to MSVC ones). svn path=/trunk/; revision=59940
2013-09-01 14:48:09 +00:00
[FRAMEDYN] - Fix MSVC build - Fix some name mangling issues - Add stub libraries to make the dll actually usable. The GCC alias library is still broken though. svn path=/trunk/; revision=60037
2013-09-11 18:36:27 +00:00
set_cpp(WITH_RUNTIME WITH_EXCEPTIONS)
if(NOT MSVC)
spec2def(framedyn.dll framedyn_gcc.spec ADD_IMPORTLIB)
else()
spec2def(framedyn.dll framedyn_msvc.spec ADD_IMPORTLIB)
endif()
list(APPEND SOURCE
main.c
chstring.cpp
${CMAKE_CURRENT_BINARY_DIR}/framedyn.def)
[SPEC2DEF] - Ignore C++ redirects again because they breaks msvcrt CORE-7465 #resolve [FRAMEDYN] - Work around the lack of C++ redirects svn path=/trunk/; revision=60135
2013-09-15 14:33:33 +00:00
if(MSVC)
add_asm_files(framedyn_asm fix_exports_msvc.s)
endif()
add_library(framedyn SHARED ${SOURCE} ${framedyn_asm})
[FRAMEDYN] Partplement framedyn.dll So far, only CHString class is implemented in it Regarding CHString class implementation: It has been implemented matching Windows behavior and bugs It might not be really nice at some points but this ensures compatibility with applications relying on it. As a side note: this might explain why this API was abandonned after w2k3... Regarding the DLL itself: Its implementation into ReactOS allows systeminfo.exe application from w2k3 to load and start initialization into ReactOS. It stops working later on with some IDispatch error. The DLL cannot be used to build any application against framedyn.dll with our "default" BE (read with G++). Only MSVC mangled name are exported so far (as on Windows ;-)) thanks to aliasing. This is why there are two spec files. This makes G++ unable to link with it though. This is the reason why there are no framedyn_apitests so far. Furthermore, the DLL only have exports for x86 and none for x64 for the moment. Any help is welcome for having exports for x64 target and to be able to have aliasing for G++ (from its mangled names to MSVC ones). svn path=/trunk/; revision=59940
2013-09-01 14:48:09 +00:00
set_module_type(framedyn win32dll UNICODE)
[FRAMEDYN] * Fix the MSVC build for real now, so that we don't keep fixing it bit by bit until r60000. svn path=/trunk/; revision=59946
2013-09-01 15:51:32 +00:00
add_importlibs(framedyn oleaut32 msvcrt kernel32 ntdll)
[FRAMEDYN] Partplement framedyn.dll So far, only CHString class is implemented in it Regarding CHString class implementation: It has been implemented matching Windows behavior and bugs It might not be really nice at some points but this ensures compatibility with applications relying on it. As a side note: this might explain why this API was abandonned after w2k3... Regarding the DLL itself: Its implementation into ReactOS allows systeminfo.exe application from w2k3 to load and start initialization into ReactOS. It stops working later on with some IDispatch error. The DLL cannot be used to build any application against framedyn.dll with our "default" BE (read with G++). Only MSVC mangled name are exported so far (as on Windows ;-)) thanks to aliasing. This is why there are two spec files. This makes G++ unable to link with it though. This is the reason why there are no framedyn_apitests so far. Furthermore, the DLL only have exports for x86 and none for x64 for the moment. Any help is welcome for having exports for x64 target and to be able to have aliasing for G++ (from its mangled names to MSVC ones). svn path=/trunk/; revision=59940
2013-09-01 14:48:09 +00:00
add_cd_file(TARGET framedyn DESTINATION reactos/system32/wbem FOR all)
[FRAMEDYN] - Fix MSVC build - Fix some name mangling issues - Add stub libraries to make the dll actually usable. The GCC alias library is still broken though. svn path=/trunk/; revision=60037
2013-09-11 18:36:27 +00:00
if(MSVC)
add_asm_files(framedynex_asm alias_msvc.s)
else()
add_asm_files(framedynex_asm alias_gcc.s)
endif()
add_library(framedynex ${framedynex_asm})
[FRAMEDYN] Fix framedynex build with msbuild, thanks ThFabba. svn path=/trunk/; revision=60390
2013-09-27 10:29:13 +00:00
set_target_properties(framedynex PROPERTIES LINKER_LANGUAGE ASM)
Reference in a new issue Copy permalink