reactos/rostests/apitests/psapi/CMakeLists.txt


list(APPEND SOURCE
    psapi.c
    testlist.c)

add_executable(psapi_apitest ${SOURCE})
set_module_type(psapi_apitest win32cui)
add_importlibs(psapi_apitest psapi msvcrt kernel32)
add_cd_file(TARGET psapi_apitest DESTINATION reactos/bin FOR all)
[PSAPI_APITEST] Add an apitest for psapi GetDeviceDriverFileName. I'm looking for help to bring it even farther. Ideally, it would be interesting to be able to GetDeviceDriverFileName on ntoskrnl base address. The whole point is about getting it dynamically. The day we can do it properly, I can predict that it will fail on ReactOS, we're not having correct paths for KDCOM, HAL, and NTOSKRNL modules in the kernel (thank you FreeLdr? - Where are you starting '\'?) svn path=/trunk/; revision=60566 2013-10-06 22:16:42 +00:00
			`list(APPEND SOURCE`
			`psapi.c`
			`testlist.c)`

			`add_executable(psapi_apitest ${SOURCE})`
			`set_module_type(psapi_apitest win32cui)`
[PSAPI_APITEST] * Speedup build. svn path=/trunk/; revision=60574 2013-10-07 12:38:42 +00:00			`add_importlibs(psapi_apitest psapi msvcrt kernel32)`
[PSAPI_APITEST] Add an apitest for psapi GetDeviceDriverFileName. I'm looking for help to bring it even farther. Ideally, it would be interesting to be able to GetDeviceDriverFileName on ntoskrnl base address. The whole point is about getting it dynamically. The day we can do it properly, I can predict that it will fail on ReactOS, we're not having correct paths for KDCOM, HAL, and NTOSKRNL modules in the kernel (thank you FreeLdr? - Where are you starting '\'?) svn path=/trunk/; revision=60566 2013-10-06 22:16:42 +00:00			`add_cd_file(TARGET psapi_apitest DESTINATION reactos/bin FOR all)`