Hello, "Reading the manuel always brings you benefit." I has verified that one more time reading in GPRBuild manual how GPR_PROJECT_PATH is processed either with UnixLike OS or with Windows. UnixLike, separator is ":", Windows it is ";". So former makefile couldn't work at all for Windows users.
Thus I've made this change and some more to deal with directory paths including space character. 1) Now for users who want to use Gnoga as a library, just do: $ make install By default installation is in "inst_folder" in current directory, it can be overridden with: $ make PREFIX=<your_path> install To install also Zanyblue and Pragmarc, you can do before: $ make zanyblue pragmarc I you don't have Sqlite3, you can do before (automatic for Windows): $ make sqlite3 And then enjoy, don't forget to set GPR_PROJECT_PATH for your installation directory. 2) I you want to play with Gnoga source code, demos, tutorials or even tests, do: $ make all And for installation, do: $ make install_debug These changes have been pushed on Gnoga SF GIT branch dev_1.3: https://sourceforge.net/p/gnoga/code/ci/dev_1.3/tree/ Could you please test it on your own environnement? Feel free to send feedback. Regards, Pascal. http://blady.pagesperso-orange.fr > Le 12 nov. 2017 à 13:35, Pascal via Gnoga-list > <gnoga-list@lists.sourceforge.net> a écrit : > > Hello Jeremiah, > > Well, I guess mingw or cygwin is expected for Gnoga. As I hadn't got full > feedbacks with full logs of these users if any, I actually don't know. > The point is that it appears that Zanyblue expected cmd window. > > Thus, I have customized the makefile with cmd.exe prefix in case of Windows, > see attached file: > > <Makefile> > > Can you please test this version 1.3 on a dedicated repository with last > dev_1.3 commit and makefile replaced by attached one? > > I haven't yet pushed it, if ok I'll pushed it to SF. > > Thanks, Pascal. > http://blady.pagesperso-orange.fr > > >> Le 10 nov. 2017 à 19:05, Jeremiah Breeden <jeremiah.bree...@gmail.com> a >> écrit : >> >> Thanks for the feedback! >> >> Perhaps a better question is what is the expected build environment for FSF >> based Gnoga on Windows? >> >> By default the command window does not have "make" nor does it have a non >> GPL version of GCC. When you built it, what did you use as an environment? >> I got mingw64 because it comes with both make and FSF GCC. If there is a >> different environment that Gnoga requires, I can try to accomodate. It >> might also be good to have something somewhere that lays out the specific >> build environment needed since base windows is not compatible. >> >> >> On Wed, Nov 8, 2017 at 1:20 PM, Pascal via Gnoga-list >> <gnoga-list@lists.sourceforge.net> wrote: >> Hello Jeremiah, >> >> Here is the answer from Zanyblue: >> "The Windows build of ZB is pretty much a Native build, not under a Unix >> style env as supplied by mingw64. Build in a cmd window is pretty much how >> I verify the build. It would be possible to detect mingw64 in the build >> process, will investigate however I do expect the a native Windows env., >> e.g., "\" instead of "/"." >> >> Zanyblue catch the OS environment variable: >> OS=Windows_NT >> >> Here are some build results under cmd window: >> >> >> >> Let me know what you think. >> >> Regards, Pascal. >> http://blady.pagesperso-orange.fr >> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Gnoga-list mailing list Gnoga-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnoga-list
