From: Rick M. <obj...@gm...> - 2015-10-21 19:49:36
|
On Wed, Oct 21, 2015 at 3:45 PM, Erich Steinböck <eri...@gm... > wrote: > NMake proceeds further but then hangs at the point below. >> > Same issue here (Windows 7). > cmake ran successfully, nmake proceeds up to > > [ 80%] Generating bin/rexx.img > > and hangs. > > I see that exactly the same issue was independently reported also by > Staffan and René last September. > > Jon, did you solve this issue? > Any ideas what I should try? > > run rexximage in the debugger and see where the hang is. Rick > Thanks, Erich > > On Wed, May 27, 2015 at 9:16 AM, Jon Wolfers <sah...@gm...> wrote: > >> Hi Jean-Louis, >> >> thanks. I updated my source and tried again. NMake proceeds further but >> then hangs at the point below. >> >> Linking CXX shared library bin\orexxole.dll >>> Creating library bin\orexxole.lib and object bin\orexxole.exp >>> [ 85%] Built target orexxole >>> Scanning dependencies of target rexx_img >>> [ 85%] Generating bin/CoreClasses.orx >>> [ 86%] Generating bin/StreamClasses.orx >>> [ 86%] Generating bin/Serializable.orx >>> [ 86%] Generating bin/PlatformObjects.orx >>> [ 86%] Generating bin/orexxole.cls >>> [ 86%] Generating bin/rexx.img >>> >> >> That looks like the problem you & RIck discuss above. I don't have time >> this morning, but will investigate tomorrow. >> >> Jon >> >> >> On 26 May 2015 at 23:59, Jean-Louis Faucher <jfa...@gm...> >> wrote: >> >>> Rick, thanks. >>> Indeed, I installed only Visual Studio Community 2013, without >>> additional sdk. >>> This version is installed by default with several sdk (from v7.0A to >>> v8.1A), and I found the file AgtCtl_i.c in the directory 'include' of >>> the sdk v7.1A. I will modify the include path to make it visible. >>> >>> Jean-Louis >>> >>> 2015-05-27 0:08 GMT+02:00 Rick McGuire <obj...@gm...>: >>> >>>> Jean-Louis, you need to install the Windows 7 SDK (download here: >>>> http://www.microsoft.com/en-us/download/details.aspx?id=3138) and make >>>> sure the sdk include directory is also added to the include path. My setup >>>> batch file I posted earlier includes that setup step, but you need the sdk >>>> installed. >>>> >>>> Rick >>>> >>>> On Tue, May 26, 2015 at 5:37 PM, Jean-Louis Faucher < >>>> jfa...@gm...> wrote: >>>> >>>>> Jon >>>>> Should compile now (tested under MacOs). >>>>> >>>>> You may have another problem when compiling >>>>> extensions/platform/windows/ole. >>>>> The fie AgtCtl_i.c is no longer delivered by Microsoft in the recent >>>>> versions of Visual C++. >>>>> If you have the problem, then you can copy the attached file in the >>>>> directory 'ole' (not to commit in svn, this is a temporary workaround). >>>>> Copied from an old version of Visual C++. >>>>> >>>>> I have seen a similar file in the public domain here : >>>>> >>>>> https://github.com/martell/i686-w64-mingw32/blob/master/i686-w64-mingw32/libsrc/agtctl_i.c >>>>> Not tested, and not sure that this file could be committed in our svn >>>>> repository. >>>>> >>>>> Jean Louis >>>>> >>>>> >>>>> 2015-05-26 19:55 GMT+02:00 Jon Wolfers <sah...@gm...>: >>>>> >>>>>> OK. I have run CMake and NMake, but the build bombs out in >>>>>> objectclass.cpp(1773) where it could not choose a suitable overload for the >>>>>> reportException call. >>>>>> >>>>>> Erich, this looks like your change 10916 for setMethod exception >>>>>> reporting. Do you need help with this? >>>>>> >>>>>> Jon >>>>>> >>>>>> On 26 May 2015 at 16:02, Rick McGuire <obj...@gm...> wrote: >>>>>> >>>>>>> Jon, no. When you do the checkout, all the rest of the stuff prior >>>>>>> to the last directory level is stripped off. So assuming your checkout was >>>>>>> done in similar fashion, then your source location would just be >>>>>>> "c:\oorexx\svn" >>>>>>> >>>>>>> Rick >>>>>>> >>>>>>> On Tue, May 26, 2015 at 10:55 AM, Jon Wolfers <sah...@gm...> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi Rick, >>>>>>>> >>>>>>>> this is good stuff. When you tell cmake where the checked out >>>>>>>> source is, where in the SVN tree do you point? >>>>>>>> >>>>>>>> Does this look right If I have my working copy in c:\ooRexx\svn? >>>>>>>> >>>>>>>> C:\oorexx\svn\code-0\main\trunk >>>>>>>> >>>>>>>> thanks >>>>>>>> >>>>>>>> Jon >>>>>>>> >>>>>>>> On 26 May 2015 at 15:15, Rick McGuire <obj...@gm...> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> A small correction to the above. I just double checked, and I am >>>>>>>>> not using an installed NSIS version after all. It is sufficient to down >>>>>>>>> load the .zip file and unzip it into a directory. >>>>>>>>> >>>>>>>>> Rick >>>>>>>>> >>>>>>>>> On Tue, May 26, 2015 at 10:08 AM, Rick McGuire < >>>>>>>>> obj...@gm...> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Tue, May 26, 2015 at 9:26 AM, Erich Steinböck < >>>>>>>>>> eri...@gm...> wrote: >>>>>>>>>> >>>>>>>>>>> can anyone lead me through building for Windows >>>>>>>>>>>> >>>>>>>>>>> I'd also be very much interested in how to build the interpreter >>>>>>>>>>> >>>>>>>>>>> How much from scratch? What do you have installed already (svn, >>>>>>>>>>>> cmake, visual studio of some flavor, nsis, etc.)? >>>>>>>>>>> >>>>>>>>>>> Until now I've just installed SVN >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Well, you will need to install some version of visual C++ (I >>>>>>>>>> recommend a recent version), One of the free express downloads is >>>>>>>>>> sufficient. You will also need Cmake (min 2.8.3 version). Optionally, you >>>>>>>>>> need a working Xerces install (although I suspect eventually you will want >>>>>>>>>> to have this). If you build the installer, you will need to also install >>>>>>>>>> NSIS. The downloads required for this can be found here: >>>>>>>>>> http://sourceforge.net/projects/oorexx/files/windows-build-tools/1.0/ >>>>>>>>>> >>>>>>>>>> Important note: When we switched to the CMake build, there's >>>>>>>>>> some stuff inside of CMake that looks for an installed version of NSIS. I >>>>>>>>>> found it necessary to download an NSIS install, then overlay that install >>>>>>>>>> with the files from the downloaded zip file. This is a special NSIS >>>>>>>>>> version that includes support for long environment strings. >>>>>>>>>> >>>>>>>>>> I used the following simple batch file to setup my build >>>>>>>>>> environment in a command window where I'm doing work. >>>>>>>>>> >>>>>>>>>> set TEST_DIR=C:\ORexxDev\testset SRC_DRV=C:set BLD_DIR=\OrexxDev\builds\%1set REXX_BUILD_HOME=%SRC_DRV%%BLD_DIR%set REXX_HOME=%SRC_DRV%%BLD_DIR%set EDITOR=notepad.execall "C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\vcvarsall.bat" x64set INCLUDE=%INCLUDE%;c:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\include;path c:\NSIS;%REXX_BUILD_HOME%\bin;%PATH%;c:\Xalan\bin;c:\Xerces\bin;%TEST_DIR%;%TEST_DIR%\framework;cd %BLD_DIR% >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> The argument to the batch file is the location of a particular >>>>>>>>>> build. The build target will know the source location you work working >>>>>>>>>> with (more on this later). This adds the build bin directory to the path, >>>>>>>>>> as well as setting up path access to all of the needed build tools. This >>>>>>>>>> version assumes the 64-bit build. To build in 32-bits, remove the x64 from >>>>>>>>>> the vcvarsall batch file call. >>>>>>>>>> >>>>>>>>>> Once you have all of the tools installed, you can build with the >>>>>>>>>> following steps. I will show the command examples using my directory >>>>>>>>>> locations just for simplicity. Replace with whatever locations you prefer >>>>>>>>>> when you set this up yourself. The following assumes >>>>>>>>>> >>>>>>>>>> 1) Check out the code into a source directory. >>>>>>>>>> >>>>>>>>>> md \OrexxDev >>>>>>>>>> cd \OrexxDev >>>>>>>>>> svn cosvn+ssh:// >>>>>>>>>> bi...@sv.../p/oorexx/code-0/main/trunk oorexx >>>>>>>>>> >>>>>>>>>> 2) Create a directory for a build target: >>>>>>>>>> >>>>>>>>>> md \OrexxDev\builds\debug >>>>>>>>>> cd \OrexxDev\builds\debug >>>>>>>>>> >>>>>>>>>> 3) configure the build directory for building using cmake >>>>>>>>>> >>>>>>>>>> (from the build target directory) >>>>>>>>>> >>>>>>>>>> cmake -G "NMake Makefiles" c:\OrexxDev\oorexx >>>>>>>>>> >>>>>>>>>> This creates a build environment that linked to the checked out >>>>>>>>>> source. You can create and configure multiple builds from a single source >>>>>>>>>> tree. For example, the above creates the debug version. To create a >>>>>>>>>> retail build: >>>>>>>>>> >>>>>>>>>> cd ..\retail >>>>>>>>>> md ..\retail >>>>>>>>>> cmake -G "NMake Makefiles" c:\OrexxDev\oorexx >>>>>>>>>> -DCMAKE_BUILD_TYPE=RELEASE >>>>>>>>>> >>>>>>>>>> Note: once you have issued the CMake command for a build target, >>>>>>>>>> you should not have to do that again. CMake is pretty good at figuring out >>>>>>>>>> when things change in the build process and reconfigures on demand. >>>>>>>>>> >>>>>>>>>> 4) Build the code >>>>>>>>>> >>>>>>>>>> (from your build directory): >>>>>>>>>> >>>>>>>>>> nmake >>>>>>>>>> >>>>>>>>>> The installer build is a separate build step. Once you have a >>>>>>>>>> clean interpreter build, issue the following command: >>>>>>>>>> >>>>>>>>>> nmake nsis_template_installers >>>>>>>>>> >>>>>>>>>> This will build the nsis installer from the build artifacts. >>>>>>>>>> Note that you do not need to install the interpreter to actually run Rexx. >>>>>>>>>> The build bin directory is already in the path, so the rexx command is >>>>>>>>>> available to you at this point. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> I tend to build things without building the installer and just >>>>>>>>>>>> run things from the build directory >>>>>>>>>>>> >>>>>>>>>>> That would be perfect for me >>>>>>>>>>> >>>>>>>>>>> At the same time I'm of course also interested in how to >>>>>>>>>>> correctly build docs. I've posted in the buildteam >>>>>>>>>>> <https://sourceforge.net/p/oorexx/discussion/buildteam/thread/52d3b56b/> >>>>>>>>>>> what my current setup is. The doc build works (I've only tested rexxref), >>>>>>>>>>> but generates literally thousands of FOP warnings/errors. So I wonder if >>>>>>>>>>> I'd need to setup something differently. I'd be grateful, if you could >>>>>>>>>>> share your experience regarding docs too >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> My experience was to rely on David for this :-) I don't know if >>>>>>>>>> it is possible to do this on Windows or not. I kept a linux virtual >>>>>>>>>> machine handy for when I needed to build the docs or just relied on David's >>>>>>>>>> build machine. David had some instructions for how to setup a machine, but >>>>>>>>>> I'm not finding it right now. Maybe David can chip in with some comments >>>>>>>>>> here. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Erich >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Tue, May 26, 2015 at 2:50 PM, Rick McGuire < >>>>>>>>>>> obj...@gm...> wrote: >>>>>>>>>>> >>>>>>>>>>>> How much from scratch? What do you have installed already >>>>>>>>>>>> (svn, cmake, visual studio of some flavor, nsis, etc.)? >>>>>>>>>>>> >>>>>>>>>>>> I tend to build things without building the installer and just >>>>>>>>>>>> run things from the build directory using a simple batch file that sets up >>>>>>>>>>>> paths appropriately. That might be simpler for you. Building the >>>>>>>>>>>> installer gets you involved with issues such as doc locations, etc. I can >>>>>>>>>>>> share that batch file with you. >>>>>>>>>>>> >>>>>>>>>>>> Rick >>>>>>>>>>>> >>>>>>>>>>>> On Tue, May 26, 2015 at 8:35 AM, Jon Wolfers < >>>>>>>>>>>> sah...@gm...> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi, >>>>>>>>>>>>> >>>>>>>>>>>>> I'm, looking for a recent 5.0.0 build for Windows (x86_32) >>>>>>>>>>>>> I want to fulfil my promise to provide a test case for the >>>>>>>>>>>>> resource directive. >>>>>>>>>>>>> >>>>>>>>>>>>> I have an installer from revision 10820 (06Nov14) taken from >>>>>>>>>>>>> the build machine, but there have been over 100 commits since then. >>>>>>>>>>>>> Does anyone have a more recent build for Windows (installer >>>>>>>>>>>>> preferred)? >>>>>>>>>>>>> >>>>>>>>>>>>> Failing that, can anyone lead me through building for Windows, >>>>>>>>>>>>> pretty much from scratch? >>>>>>>>>>>>> >>>>>>>>>>>>> thanks, >>>>>>>>>>>>> >>>>>>>>>>>>> Jon >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>>>> One dashboard for servers and applications across >>>>>>>>>>>>> Physical-Virtual-Cloud >>>>>>>>>>>>> Widest out-of-the-box monitoring support with 50+ applications >>>>>>>>>>>>> Performance metrics, stats and reports that give you >>>>>>>>>>>>> Actionable Insights >>>>>>>>>>>>> Deep dive visibility with transaction tracing using APM >>>>>>>>>>>>> Insight. >>>>>>>>>>>>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Oorexx-devel mailing list >>>>>>>>>>>>> Oor...@li... >>>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>>> One dashboard for servers and applications across >>>>>>>>>>>> Physical-Virtual-Cloud >>>>>>>>>>>> Widest out-of-the-box monitoring support with 50+ applications >>>>>>>>>>>> Performance metrics, stats and reports that give you Actionable >>>>>>>>>>>> Insights >>>>>>>>>>>> Deep dive visibility with transaction tracing using APM Insight. >>>>>>>>>>>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Oorexx-devel mailing list >>>>>>>>>>>> Oor...@li... >>>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>>>> One dashboard for servers and applications across >>>>>>>>>>> Physical-Virtual-Cloud >>>>>>>>>>> Widest out-of-the-box monitoring support with 50+ applications >>>>>>>>>>> Performance metrics, stats and reports that give you Actionable >>>>>>>>>>> Insights >>>>>>>>>>> Deep dive visibility with transaction tracing using APM Insight. >>>>>>>>>>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Oorexx-devel mailing list >>>>>>>>>>> Oor...@li... >>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>> One dashboard for servers and applications across >>>>>>>>> Physical-Virtual-Cloud >>>>>>>>> Widest out-of-the-box monitoring support with 50+ applications >>>>>>>>> Performance metrics, stats and reports that give you Actionable >>>>>>>>> Insights >>>>>>>>> Deep dive visibility with transaction tracing using APM Insight. >>>>>>>>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >>>>>>>>> _______________________________________________ >>>>>>>>> Oorexx-devel mailing list >>>>>>>>> Oor...@li... >>>>>>>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> One dashboard for servers and applications across >>>>>>>> Physical-Virtual-Cloud >>>>>>>> Widest out-of-the-box monitoring support with 50+ applications >>>>>>>> Performance metrics, stats and reports that give you Actionable >>>>>>>> Insights >>>>>>>> Deep dive visibility with transaction tracing using APM Insight. >>>>>>>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >>>>>>>> _______________________________________________ >>>>>>>> Oorexx-devel mailing list >>>>>>>> Oor...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> One dashboard for servers and applications across >>>>>> Physical-Virtual-Cloud >>>>>> Widest out-of-the-box monitoring support with 50+ applications >>>>>> Performance metrics, stats and reports that give you Actionable >>>>>> Insights >>>>>> Deep dive visibility with transaction tracing using APM Insight. >>>>>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >>>>>> _______________________________________________ >>>>>> Oorexx-devel mailing list >>>>>> Oor...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>>>>> >>>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> >>>>> _______________________________________________ >>>>> Oorexx-devel mailing list >>>>> Oor...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>>>> >>>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> Oorexx-devel mailing list >>>> Oor...@li... >>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>>> >>>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Oorexx-devel mailing list >>> Oor...@li... >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> >>> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > |