Compiling RTI Perftest with DDS Micro

Have you set the required environment variables?

Please see Section 3.2.1

https://community.rti.com/static/documentation/perftest/current/compilation.html

specifically,

• The %NDDSHOME% environment variable should be set correctly. Alternatively, %NDDSHOME% can be passed directly to the build.bat script by using the --nddshome <PATH> command-line option.

  When compiling for RTI Connext DDS Micro, the %RTIMEHOME% environment variable should be set correctly. Alternatively, %RTIMEHOME% can be passed directly to the build.bat script by using the --rtimehome <PATH> command-line option.

Hello,

I think you removed the wrong option, lets check this out:

The problem seems to come from the following part of the build script:

	if x!CMAKE_GENERATOR! == x"NMake Makefiles" (
		echo[
		echo [INFO]: Using NMake for the CMake generator, use --cmake-generator to specify other.
	)
	cd "%classic_cpp_folder%"
	call !CMAKE_EXE! -DCMAKE_BUILD_TYPE=!RELEASE_DEBUG! --target perftest_publisher -G !CMAKE_GENERATOR! !ADDITIONAL_CMAKE_ARGS! -B./perftest_build -H. -DRTIME_TARGET_NAME=%architecture% -DPLATFORM_LIBS="netapi32.lib;advapi32.lib;user32.lib;winmm.lib;WS2_32.lib;"
	if not !ERRORLEVEL! == 0 (
		echo [ERROR]: Failure compiling code for %classic_cpp_lang_string%.
		cd ..
		exit /b 1
	)

	call !CMAKE_EXE! --build ./perftest_build --config !RELEASE_DEBUG! --target perftest_publisher
	if not !ERRORLEVEL! == 0 (
		echo [ERROR]: Failure compiling code for %classic_cpp_lang_string%.
		cd ..
		exit /b 1
	)
	cd ..

There, is where we pass the "target" to cmake. It is weird that it is not finding it in your case, but I think you can potentially just remove 

--target perftest_publisher

And still being able to build. Can you check this out? Make sure you do a "git clean -xdf" prior to rebuild (to clean all the cmake cache files).

Oh, btw, make sure to remove in both calls to CMAKE, in the generation and in the build steps.

Hi, sorry, I thought you deleted something else, hence asking you to repeat the same steps, my apologies.

This error is indeed extrange, but I have some hints: I believe the problem might be due to nmake being an x86 application (given the path), maybe it is not able to compile x64 stuff. We could potentially try the following:

- CMake has the option to generate the output as a Visual Studio Solution (we don't use such option because it is quite dependent on the VS and CMake installed, that is why we default always to NMake). You can check which options you have for the generators by doing: "cmake -h" and check the "Generators" section. You will probably have specific ones for Visual Studio, choose one (and make sure to add the x64, so it does not generate the code for x32, those are listed by pairs if I recall correctly).

- Either use the command line option in the build.bat to pass the name of the compiler or just override the CMAKE_GENERATOR variable it in the build script, here, in the -G !CMAKE_GENERATOR!

	call !CMAKE_EXE! -DCMAKE_BUILD_TYPE=!RELEASE_DEBUG! --target perftest_publisher -G !CMAKE_GENERATOR! !ADDITIONAL_CMAKE_ARGS! -B./perftest_build -H. -DRTIME_TARGET_NAME=%architecture% -DPLATFORM_LIBS="netapi32.lib;advapi32.lib;user32.lib;winmm.lib;WS2_32.lib;"

Optionally, after that same call add a stop for the script to continue doing everything manually:

exit /b 1

And open the Visual Studio Solution (from a terminal where your RTIMEHOME variable is set) and compile it graphically with Visual Studio or with MSbuild.

Let me know how it goes with this method.

Ok... so now you are generating the solution, did you add the exit call I mentioned to you? Then do you open the .sln from the terminal with Visual Studio or what do you do?

> Graphically I believe there should be on the top part a section where it allows you to select debug or release, isn't that selected, it should be "Release".

> If you are using CMake to build, I think you need to add 

--config Release

Good! At least we see some progress there.

I was wondering if you built the Micro libraries both for release and debug. Could it be possible that you only built Micro for debug and not release? I would expect to see different errors there, but it is true that I have not dealt with these issues before.

Alternatively, I googled the linker error a bit and I got a couple of hits, not sure if any of them will fit your use-case, but it might be worth trying. Disclaimer: usually building Perftest for Micro on Windows is painless. I am not sure why your configuration is giving us so much trouble!

These were the 2 things I found for:

error LNK2001: unresolved external symbol _purecall

Ans1> The problem comes from /NOENTRY option in Project Properties->Linker->Advanced->No Entry Point. Removing it solved the problem

Ans2> It seems like my problem was that I was using the /NODEFAULTLIB argument, and removing that made the errors go away.

Hmmm...

Could you check what are the flags that change between release and debug in the solution? It must be one of these, since the target libraries will be the same in both cases and with debug you are able to compile.

Glad to know you resolved this!

In any case, I discussed your issue with our Micro team and they mentioned they were able to reproduce this issue, but it got solved by using the Visual Studio Command line prompt (the one for Native x64 builds), with no need to performn changes in the build script. It might be worth giving it a try if you were not using it already.

Regards,

Javi