Ok, poking around in the generated build files, I found the definition of CXX_FLAGS in rexxapi.dir\flags.make. Here it is:CXX_FLAGS = /DWIN32 /D_WINDOWS /W3 /GR /EHsc /D_DEBUG /MDd /Zi /Ob0 /Od /RTC1 -IC:\ORexxDev\oorexx\api\platform\windows -IC:\ORexxDev\oorexx\apiThe only include directories specified are the main api directories. None of the cross project directories are included, causing the compile errors.RickOn Thu, May 1, 2014 at 6:30 AM, Rick McGuire <firstname.lastname@example.org> wrote:
OK, figured out how to get it go generate nmake files. The secret is to add -G "NMake Makefiles" to the cmake command. Again, this generated without error, but when I run nmake, it again gives compile errors that appear to indicate the include path is not getting setup correctly. Here is the build output:C:\ORexxDev\oorexx>nmakeMicrosoft (R) Program Maintenance Utility Version 12.00.21005.1Copyright (C) Microsoft Corporation. All rights reserved.Scanning dependencies of target rexxapi[ 4%] Building CXX object CMakeFiles/rexxapi.dir/rexxapi/client/ClientMessage.cpp.objClientMessage.cppc:\orexxdev\oorexx\rexxapi\client\ClientMessage.hpp(43) : fatal error C1083: Cannot open include file: 'ServiceMessage.hpp': No such file or directoryNMAKE : fatal error U1077: 'C:\PROGRA~2\MICROS~3.0\VC\bin\cl.exe' : return code'0x2'Stop.NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN\amd64\nmake.exe"' : return code '0x2'Stop.NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN\amd64\nmake.exe"' : return code '0x2'Stop.On Thu, May 1, 2014 at 6:18 AM, Rick McGuire <email@example.com> wrote:
Just did this, and it looks like there is a problem if you have the full visual studio installed. It is generating a Visual Studio project rather than a makefile. I opened that project in VS, and it did not build cleanly because it was not finding any of the project header files that needed to be pulled from other project directories. For example, ServiceException.hpp.Is there a way to force it to generate a traditional makefile rather than the visual studio project?On the plus side, I didn't see any warnings while it was building the wrong thing :-)RickOn Wed, Apr 30, 2014 at 8:42 PM, David Ashley <firstname.lastname@example.org> wrote:
I just committed a CMake starter file to the repository. There is only
one file you need to build with CMake. Currently CMake only builds the
rexxapi shared library (I had to start somewhere).
To get started:
1. Download and install CMake. If you do this on Linux try to use the
CMake that comes with your distribution. On Windows go to
http://www.cmake.org/ and download the Windows install file.
2. Run cmake ./ from the ooRexx svn trunk. Ignore the warning messages
as I will be fixing those later and they do not impact building the
rexxapi shared library.
3. Run make on Linux or nmake on Windows (from the trunk as well).
The rexxapi shared library (DLL) will be placed in the CMakeFiles/bin
subdirectory if the build is successful.
Please let me know if you have any problems.
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
Oorexx-devel mailing list