Okay, yeah I discovered the temp files. Unfortunately during the build the
files get deleted to fast to look at them.
--
Mark Miesfeld
On Sun, Jun 15, 2014 at 2:21 PM, Rick McGuire <object.r...@gmail.com> wrote:
> Shoot, I stand corrected. It appears nmake writes all of the options to a
> temp file and uses
>
> C:\PROGRA~2\MICROS~3.0\VC\bin\amd64\cl.exe
> @C:\Users\RICKMC~1\AppData\L
> ocal\Temp\nm4144.tmp
>
> to invoke the compler and linker. The options are not showing up in
> verbose mode. This will probably require some digging in the make file. I
> need to leave fairly shortly and will be gone for the rest of the evening,
> however, each executable has a build.make file in a target dir. So, for
> example, rexx.dll is in CMakeFiles\rexx.dir. You might be able to add an
> echo instruction to the make file to display the current value of CXX_FLAGS
> to see what is getting used. We're pretty much using the defaults for the
> different profiles now, but they are easy to customize.
>
> Rick
>
>
> On Sun, Jun 15, 2014 at 5:10 PM, Mark Miesfeld <miesf...@gmail.com> wrote:
>
>> Thanks Rick.
>>
>> --
>> Mark Miesfeld
>>
>>
>> On Sun, Jun 15, 2014 at 2:06 PM, Rick McGuire <object.r...@gmail.com>
>> wrote:
>>
>>> If you want to see what are getting used for the compile and links, you
>>> can specify "nmake VERBOSE=1", and it will display all of the commands that
>>> nmake is issuing. This allows you to see the exact commands getting issued
>>> for the build steps.
>>>
>>> Rick
>>>
>>>
>>> On Sun, Jun 15, 2014 at 4:37 PM, Mark Miesfeld <miesf...@gmail.com>
>>> wrote:
>>>
>>>> With the same code base, when I run the test suite against 4.3.0 built
>>>> with CMake, the interpreter crashes every time. Not always in the same
>>>> spot, but every time.
>>>>
>>>> Running the test suite against 4.3.0 built using the old .bat process,
>>>> the interpreter never crashes. It does have a lot of test failures, but it
>>>> never crashes. (Maybe I shouldn't say never, but it is 0 out of 10.)
>>>>
>>>> I think maybe the CMake build is not using the correct compile/link
>>>> flags for ooRexx. Is there a way to display the command line during the
>>>> comple/link phases?
>>>>
>>>> In particular, I believe, we will have problems if CMake is dynamically
>>>> linking to the CRT.
>>>>
>>>> You can see that the executables are getting build different by just
>>>> comparing the sizes of the files:
>>>>
>>>> CMake debug build:
>>>>
>>>> C:\Rexx>dir ooRexx\*.dll
>>>> Volume in drive C is Win7
>>>> Volume Serial Number is D25E-50D5
>>>>
>>>> Directory of C:\Rexx\ooRexx
>>>>
>>>> 06/15/2014 12:11 PM 52,224 hostemu.dll
>>>> 06/15/2014 12:12 PM 1,527,296 oodialog.dll
>>>> 06/15/2014 12:12 PM 158,208 orexxole.dll
>>>> 06/15/2014 12:11 PM 2,123,264 rexx.dll
>>>> 06/15/2014 12:08 PM 215,040 rexxapi.dll
>>>> 06/15/2014 12:12 PM 156,672 rexxutil.dll
>>>> 06/15/2014 12:12 PM 52,224 rxmath.dll
>>>> 06/15/2014 12:12 PM 58,368 rxregexp.dll
>>>> 06/15/2014 12:12 PM 81,920 rxsock.dll
>>>> 06/15/2014 12:12 PM 154,112 rxwinsys.dll
>>>> 10 File(s) 4,579,328 bytes
>>>> 0 Dir(s) 1,773,953,024 bytes free
>>>>
>>>> .bat file style build:
>>>>
>>>> C:\Rexx>dir ooRexx.4.3.0.debug-oldStyle\*.dll
>>>> Volume in drive C is Win7
>>>> Volume Serial Number is D25E-50D5
>>>>
>>>> Directory of C:\Rexx\ooRexx.4.3.0.debug-oldStyle
>>>>
>>>> 06/15/2014 09:54 AM 236,032 hostemu.dll
>>>> 06/15/2014 09:55 AM 1,241,600 oodialog.dll
>>>> 06/15/2014 09:54 AM 313,344 orexxole.dll
>>>> 06/15/2014 09:54 AM 1,717,248 rexx.dll
>>>> 06/15/2014 09:50 AM 372,736 rexxapi.dll
>>>> 06/15/2014 09:54 AM 395,776 rexxutil.dll
>>>> 06/15/2014 09:54 AM 289,792 rxmath.dll
>>>> 06/15/2014 09:54 AM 195,584 rxregexp.dll
>>>> 06/15/2014 09:54 AM 238,080 rxsock.dll
>>>> 06/15/2014 09:54 AM 311,808 rxwinsys.dll
>>>> 10 File(s) 5,312,000 bytes
>>>> 0 Dir(s) 1,773,953,024 bytes free
>>>>
>>>> Looking at the CMake files, it looks to me like none of the extension
>>>> DLLs are built as debug files. But, rexx.dll and oodialog.dll are much
>>>> larger than the old style build, indicating the compile and/or link flags
>>>> are different.
>>>>
>>>> makeorx works with the current head. It just leaves out some of the
>>>> newer samples that Rick added.
>>>>
>>>> I used testOORexx.rex -B as the command line for the test suite.
>>>>
>>>> The CMake build will work with the test suite as long as you build an
>>>> install package and install it.
>>>>
>>>> Otherwise, if you don't want to install the package, you can set
>>>> REXX_HOME to point to the out-of-source build directory like this:
>>>>
>>>> set REXX_HOME=C:\work.ooRexx\wc\build.debug\NSIS\files\DevLib
>>>>
>>>> but, you have to at least build the NSIS installer for that to work.
>>>> If things aren't right, when the external API libraries are built, the
>>>> header files won't be found.
>>>>
>>>> --
>>>> Mark Miesfeld
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> HPCC Systems Open Source Big Data Platform from LexisNexis Risk
>>>> Solutions
>>>> Find What Matters Most in Your Big Data with HPCC Systems
>>>> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
>>>> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
>>>> http://p.sf.net/sfu/hpccsystems
>>>> _______________________________________________
>>>> Oorexx-devel mailing list
>>>> Oorexx-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>>
>>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
>>> Find What Matters Most in Your Big Data with HPCC Systems
>>> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
>>> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
>>> http://p.sf.net/sfu/hpccsystems
>>> _______________________________________________
>>> Oorexx-devel mailing list
>>> Oorexx-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
>> Find What Matters Most in Your Big Data with HPCC Systems
>> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
>> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
>> http://p.sf.net/sfu/hpccsystems
>> _______________________________________________
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>>
>
>
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
