Tested on 64-bit ooRexx as well and works like a charm, kudos to Enrico!
---
So a little roundup:
* Enrico's CMake sample works on Windows as well, tested with both the 32 and
64 bit Microsoft
compiler!!
* Windows specifics:
o the ooRexx installation copies the *.h and *.lib files to a directory
named "api"
+ suggestion: create an "include" (for the *.h files) and a "lib"
(for the *lib files)
directory on Windows instead of the "api" directory
o the classic Rexx libraries need the loader function exported, pre
ooRexx 5 interpreters need
the RexxGetPackage function exported: solution, needing at least CMake
version 3.3: add the
switch "-DCMAKE_WINDOWS_EXPORT_ALL_SYMBOLS=TRUE"
+ would suggest to use that switch for both, the classic and native
libraries to allow
them to be usable by earlier versions of
o to compile the 32- and the 64-bit versions I used the
"USB"-installation versions of ooRexx.
Now that it has become possible (kudos to Rick!) to run 32- and 64-bit
ooRexx in parallel on
the same machine, this excercise has become very, very easy/efficient,
a real great and
important boon!
This will allow me to experiment with the creation of the BSF4ooRexx and
dbusoorexx libraries for
all platforms including Windows, which may become a breeze!
---rony
P.S.: Still, this will take some time as the day-job work-load increases due to
the beginning of the
summer semester around here.
On 18.02.2019 17:39, Rony G. Flatscher wrote:
> On 18.02.2019 17:22, Enrico Sorichetti via Oorexx-devel wrote:
>> Dear Rony
>> I am very happy that it was useful
>>
>> Looking at the status of variable for complex cmakelists
>> ( and I wrote a couple of them )
>> Is usually the only way to debug cmakelists errors
>>
>> The vdump module was the first one I wrote a long time ago
>> To get a better knowledge of the cmake ways
>>
>> Using cmake -G should have caused different errors IIRC
>>
>> It tells to cmake which generator is being used,
>> ( I usually go with cmake -G Ninja … … … )
>> So I do not see why it should meddle with the compiler options
>>
>> I will push an update to include the proper defaults for the c / c++
>> compilers
>> ( obviously the msvc stuff will empty )
>>
>> Just look at the README, I posted two different CMakeLists
>> A minimal and a platinum , the minimal does al that is needed with no frills
>
> Hmm, just see probably the "minimal" which is ideal for a newbie to CMake
> like myself! :)
>
> Researching about the exported symbols problem on Windows I ran around the
> following switch
> "-DCMAKE_WINDOWS_EXPORT_ALL_SYMBOLS=TRUE", which solves the problem for the
> classic library
> problem. Now both Rexx scripts work:
>
> cmake -G "NMake Makefiles" -DCMAKE_WINDOWS_EXPORT_ALL_SYMBOLS=TRUE
> -DOOREXX_INSTALL_PREFIX=%OOREXX_HOME_32% ..\rxSnippets
> ...
> nmake
> ...
> G:\oorexx.tmp\enrico\win32>rexx rxClassic
> rxClassicVersion at line 84' '1.0.0'
>
> 1.0.0
> rxClassicWorker at line 103'
> Argc 0
>
> rxClassicWorker at line 103'
> Argc 1
> Argv 0 'A'
>
> rxClassicWorker at line 103'
> Argc 2
> Argv 0 'A'
> Argv 1 'B'
>
>
> G:\oorexx.tmp\enrico\win32>rexx rxClassic
> rxClassicVersion at line 84' '1.0.0'
>
> 1.0.0
> rxClassicWorker at line 103'
> Argc 0
>
> rxClassicWorker at line 103'
> Argc 1
> Argv 0 'A'
>
> rxClassicWorker at line 103'
> Argc 2
> Argv 0 'A'
> Argv 1 'B'
>
>
> G:\oorexx.tmp\enrico\win32>
>
> This is really just *great*, thank you very much indeed!
>
> ---rony
>
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
