From: Rick M. <obj...@gm...> - 2015-05-26 14:15:32
|
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 >> >> > |