From: Rick M. <obj...@gm...> - 2014-04-21 13:24:34
|
I've not liked the lack of dependency management in the makefiles used for building Windows for quite a while. David spent quite a bit of time trying to get a Windows build working with autoconf and never really got things working. I'm sort of thinking we might be able to do this as a manual process by taking the Makefile generated for Linux and manually converting it into a Windows makefile. At first glance, this doesn't really look to be that bad. There are a lot of changes to make, but mostly of the repetitive variety. Once converted, we'll have a make file with all of the dependencies created. This will still need to manually updated in the future, but we'll have a make file that operates better than the one we're using now (which for all intents, is 25 years old). Hopefully, we'll be able to keep this skewing too much from the autoconf generated one. It might even be an interesting exercise to write a tool to sync the dependencies up again. Left as a exercise to the reader! I'm willing to take a crack at converting to see if this is workable. The autoconf generated make file builds all of the project from the single makefile, while on Windows, we have separate makefiles for each of the subprojects (e.g., various extensions like rxsock, rxmath, etc.). I can go either way on the port, though I suspect as a first step, I'll create a combined make. Note that this will not cover the Windows-only extensions because the Linux Makefile does not have anything generated for those directories. Any opinions on the single file/multiple file question? Rick |
From: Mark M. <mie...@gm...> - 2014-04-21 13:35:56
|
Sounds like a reasonable project. I'd say go for the single file to start with. -- Mark Miesfeld On Mon, Apr 21, 2014 at 6:24 AM, Rick McGuire <obj...@gm...> wrote: > I've not liked the lack of dependency management in the makefiles used for > building Windows for quite a while. David spent quite a bit of time trying > to get a Windows build working with autoconf and never really got things > working. I'm sort of thinking we might be able to do this as a manual > process by taking the Makefile generated for Linux and manually converting > it into a Windows makefile. At first glance, this doesn't really look to > be that bad. There are a lot of changes to make, but mostly of the > repetitive variety. Once converted, we'll have a make file with all of the > dependencies created. This will still need to manually updated in the > future, but we'll have a make file that operates better than the one we're > using now (which for all intents, is 25 years old). Hopefully, we'll be > able to keep this skewing too much from the autoconf generated one. It > might even be an interesting exercise to write a tool to sync the > dependencies up again. Left as a exercise to the reader! I'm willing to > take a crack at converting to see if this is workable. > > The autoconf generated make file builds all of the project from the single > makefile, while on Windows, we have separate makefiles for each of the > subprojects (e.g., various extensions like rxsock, rxmath, etc.). I can go > either way on the port, though I suspect as a first step, I'll create a > combined make. Note that this will not cover the Windows-only extensions > because the Linux Makefile does not have anything generated for those > directories. Any opinions on the single file/multiple file question? > > Rick > > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > |
From: David A. <w.d...@gm...> - 2014-04-21 14:33:47
|
I would like to give the autotools on Windows another try. The last time I did this I was still struggling with getting to know the autotools family of apps so I ran into some roadblocks I did not have enough knowledge to resolve. Since then I have gained enough experience that I think I can overcome my original problems. Of course, the primary problem with using autotools is that Cygwin is a prerequisite. I do not have a problem with this but others might have. IMHO having a single build source is the best solution. But that is just my opinion and I certainly respect the opinion of others. David Ashley On Mon, 2014-04-21 at 09:24 -0400, Rick McGuire wrote: > I've not liked the lack of dependency management in the makefiles used > for building Windows for quite a while. David spent quite a bit of > time trying to get a Windows build working with autoconf and never > really got things working. I'm sort of thinking we might be able to > do this as a manual process by taking the Makefile generated for Linux > and manually converting it into a Windows makefile. At first glance, > this doesn't really look to be that bad. There are a lot of changes > to make, but mostly of the repetitive variety. Once converted, we'll > have a make file with all of the dependencies created. This will > still need to manually updated in the future, but we'll have a make > file that operates better than the one we're using now (which for all > intents, is 25 years old). Hopefully, we'll be able to keep this > skewing too much from the autoconf generated one. It might even be an > interesting exercise to write a tool to sync the dependencies up > again. Left as a exercise to the reader! I'm willing to take a crack > at converting to see if this is workable. > > > The autoconf generated make file builds all of the project from the > single makefile, while on Windows, we have separate makefiles for each > of the subprojects (e.g., various extensions like rxsock, rxmath, > etc.). I can go either way on the port, though I suspect as a first > step, I'll create a combined make. Note that this will not cover the > Windows-only extensions because the Linux Makefile does not have > anything generated for those directories. Any opinions on the single > file/multiple file question? > > > Rick > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel |
From: Rick M. <obj...@gm...> - 2014-04-21 14:38:38
|
I'd love to have a single source too. Perhaps we could checkin the autogenerated Windows version so that cygwin is only required for people who actually make changes to the makefiles. Rick On Mon, Apr 21, 2014 at 10:33 AM, David Ashley <w.d...@gm...>wrote: > I would like to give the autotools on Windows another try. The last time > I did this I was still struggling with getting to know the autotools > family of apps so I ran into some roadblocks I did not have enough > knowledge to resolve. Since then I have gained enough experience that I > think I can overcome my original problems. > > Of course, the primary problem with using autotools is that Cygwin is a > prerequisite. I do not have a problem with this but others might have. > > IMHO having a single build source is the best solution. But that is just > my opinion and I certainly respect the opinion of others. > > David Ashley > > On Mon, 2014-04-21 at 09:24 -0400, Rick McGuire wrote: > > I've not liked the lack of dependency management in the makefiles used > > for building Windows for quite a while. David spent quite a bit of > > time trying to get a Windows build working with autoconf and never > > really got things working. I'm sort of thinking we might be able to > > do this as a manual process by taking the Makefile generated for Linux > > and manually converting it into a Windows makefile. At first glance, > > this doesn't really look to be that bad. There are a lot of changes > > to make, but mostly of the repetitive variety. Once converted, we'll > > have a make file with all of the dependencies created. This will > > still need to manually updated in the future, but we'll have a make > > file that operates better than the one we're using now (which for all > > intents, is 25 years old). Hopefully, we'll be able to keep this > > skewing too much from the autoconf generated one. It might even be an > > interesting exercise to write a tool to sync the dependencies up > > again. Left as a exercise to the reader! I'm willing to take a crack > > at converting to see if this is workable. > > > > > > The autoconf generated make file builds all of the project from the > > single makefile, while on Windows, we have separate makefiles for each > > of the subprojects (e.g., various extensions like rxsock, rxmath, > > etc.). I can go either way on the port, though I suspect as a first > > step, I'll create a combined make. Note that this will not cover the > > Windows-only extensions because the Linux Makefile does not have > > anything generated for those directories. Any opinions on the single > > file/multiple file question? > > > > > > Rick > > > ------------------------------------------------------------------------------ > > Start Your Social Network Today - Download eXo Platform > > Build your Enterprise Intranet with eXo Platform Software > > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > > Get Started Now And Turn Your Intranet Into A Collaboration Platform > > http://p.sf.net/sfu/ExoPlatform > > _______________________________________________ > > Oorexx-devel mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
From: Michael L. <ml...@lu...> - 2014-04-21 14:53:30
|
David Ashley wrote: > Of course, the primary problem with using autotools is that Cygwin is a > prerequisite. Is there no native port of autotools to Windows, corresponding/similar to SourceForge projects: http://gnuwin32.sourceforge.net/ or http://unxutils.sourceforge.net/ ? Are you proposing just swapping out the tools and leave the compiler used as MS, or transitioning over to the Gnu or similar compiler also? I am thankful, -- Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/ |
From: Rick M. <obj...@gm...> - 2014-04-21 15:04:33
|
No, the build will still need to be done us MS tools. The only thing that we really want to change is the maintenance of the makefile. Rick On Mon, Apr 21, 2014 at 10:40 AM, Michael Lueck <ml...@lu... > wrote: > David Ashley wrote: > > Of course, the primary problem with using autotools is that Cygwin is a > > prerequisite. > > > Is there no native port of autotools to Windows, corresponding/similar to > SourceForge projects: http://gnuwin32.sourceforge.net/ or > http://unxutils.sourceforge.net/ ? > > Are you proposing just swapping out the tools and leave the compiler used > as MS, or transitioning over to the Gnu or similar compiler also? > > I am thankful, > > -- > Michael Lueck > Lueck Data Systems > http://www.lueckdatasystems.com/ > > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
From: Michael L. <ml...@lu...> - 2014-04-21 15:12:26
|
Greetings Rick, Rick McGuire wrote: > The only thing that we really want to change is the maintenance of the makefile. Thank you for clarification. I was interested that would it become possible to build ooRexx for Windows without having a copy of MS C++ handy. I am thankful, -- Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/ |
From: David A. <w.d...@gm...> - 2014-04-21 15:33:13
|
I fully agree with Rick. We need to find a way to use the MS tools natively under autotools/Cygwin. I also agree the checking in the final makefile to SVN would be a good idea. There might be a problem with that because the autotools automake app generates code for the standard make utility, not the MS nmake utility. The code might be compatible or it might not, we will just have to wait and see what the results are. David Ashley On Mon, 2014-04-21 at 11:12 -0400, Michael Lueck wrote: > Greetings Rick, > > Rick McGuire wrote: > > The only thing that we really want to change is the maintenance of the makefile. > > > Thank you for clarification. I was interested that would it become possible to build ooRexx for Windows without having a copy of MS C++ handy. > > I am thankful, > |
From: David A. <w.d...@gm...> - 2014-04-21 16:11:51
|
Ok, new train of thought, same subject. What about eliminating aototools completely? There are other, more portable build environments available these days. CMake springs to mind immediately. It is a lot easier to use, portable across multiple environment including Windows and Linux, and can maintain dependencies automatically (at least most of them). It also natively uses the compiler, linker and other tools to build the application(s). http://www.cmake.org/ There are some other build environments available but CMake appears to be the most used and is free to download and use. What do you think? David Ashley |
From: Rick M. <obj...@gm...> - 2014-04-21 16:16:17
|
I certainly have no particular ties to autotools. My only reservations about switching to something else would be to ensure it is ubiquitous enough. For example, would cmake be available for environments such as z-linux or AIX? Rick On Mon, Apr 21, 2014 at 12:11 PM, David Ashley <w.d...@gm...>wrote: > Ok, new train of thought, same subject. > > What about eliminating aototools completely? There are other, more > portable build environments available these days. CMake springs to mind > immediately. It is a lot easier to use, portable across multiple > environment including Windows and Linux, and can maintain dependencies > automatically (at least most of them). It also natively uses the > compiler, linker and other tools to build the application(s). > > http://www.cmake.org/ > > There are some other build environments available but CMake appears to > be the most used and is free to download and use. > > What do you think? > > David Ashley > > > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
From: David A. <w.d...@gm...> - 2014-04-21 16:28:22
|
It is available for Linux x86 Mac OSX Windows AIX IRIX Most Linux distribution provide via their repositories. The source is also available for building it on other platforms. David Ashley On Mon, 2014-04-21 at 12:16 -0400, Rick McGuire wrote: > I certainly have no particular ties to autotools. My only > reservations about switching to something else would be to ensure it > is ubiquitous enough. For example, would cmake be available for > environments such as z-linux or AIX? > > > Rick > > > On Mon, Apr 21, 2014 at 12:11 PM, David Ashley > <w.d...@gm...> wrote: > Ok, new train of thought, same subject. > > What about eliminating aototools completely? There are other, > more > portable build environments available these days. CMake > springs to mind > immediately. It is a lot easier to use, portable across > multiple > environment including Windows and Linux, and can maintain > dependencies > automatically (at least most of them). It also natively uses > the > compiler, linker and other tools to build the application(s). > > http://www.cmake.org/ > > There are some other build environments available but CMake > appears to > be the most used and is free to download and use. > > What do you think? > > David Ashley > > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud > Ready > Get Started Now And Turn Your Intranet Into A Collaboration > Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel |
From: Rick M. <obj...@gm...> - 2014-04-21 16:42:12
|
Sounds doable to me. Rick On Mon, Apr 21, 2014 at 12:28 PM, David Ashley <w.d...@gm...>wrote: > It is available for > > Linux x86 > Mac OSX > Windows > AIX > IRIX > > Most Linux distribution provide via their repositories. The source is > also available for building it on other platforms. > > David Ashley > > On Mon, 2014-04-21 at 12:16 -0400, Rick McGuire wrote: > > I certainly have no particular ties to autotools. My only > > reservations about switching to something else would be to ensure it > > is ubiquitous enough. For example, would cmake be available for > > environments such as z-linux or AIX? > > > > > > Rick > > > > > > On Mon, Apr 21, 2014 at 12:11 PM, David Ashley > > <w.d...@gm...> wrote: > > Ok, new train of thought, same subject. > > > > What about eliminating aototools completely? There are other, > > more > > portable build environments available these days. CMake > > springs to mind > > immediately. It is a lot easier to use, portable across > > multiple > > environment including Windows and Linux, and can maintain > > dependencies > > automatically (at least most of them). It also natively uses > > the > > compiler, linker and other tools to build the application(s). > > > > http://www.cmake.org/ > > > > There are some other build environments available but CMake > > appears to > > be the most used and is free to download and use. > > > > What do you think? > > > > David Ashley > > > > > > > ------------------------------------------------------------------------------ > > Start Your Social Network Today - Download eXo Platform > > Build your Enterprise Intranet with eXo Platform Software > > Java Based Open Source Intranet - Social, Extensible, Cloud > > Ready > > Get Started Now And Turn Your Intranet Into A Collaboration > > Platform > > http://p.sf.net/sfu/ExoPlatform > > _______________________________________________ > > Oorexx-devel mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > > > > > ------------------------------------------------------------------------------ > > Start Your Social Network Today - Download eXo Platform > > Build your Enterprise Intranet with eXo Platform Software > > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > > Get Started Now And Turn Your Intranet Into A Collaboration Platform > > http://p.sf.net/sfu/ExoPlatform > > _______________________________________________ > > Oorexx-devel mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |
From: René J. <rvj...@xs...> - 2014-04-21 16:45:34
|
just installed it on Linux-ARM (Raspbian) via apt-get install cmake, works fine. Someone should check z/Linux. René. On 21 apr. 2014, at 18:28, David Ashley <w.d...@gm...> wrote: > It is available for > > Linux x86 > Mac OSX > Windows > AIX > IRIX > > Most Linux distribution provide via their repositories. The source is > also available for building it on other platforms. > > David Ashley > > On Mon, 2014-04-21 at 12:16 -0400, Rick McGuire wrote: >> I certainly have no particular ties to autotools. My only >> reservations about switching to something else would be to ensure it >> is ubiquitous enough. For example, would cmake be available for >> environments such as z-linux or AIX? >> >> >> Rick >> >> >> On Mon, Apr 21, 2014 at 12:11 PM, David Ashley >> <w.d...@gm...> wrote: >> Ok, new train of thought, same subject. >> >> What about eliminating aototools completely? There are other, >> more >> portable build environments available these days. CMake >> springs to mind >> immediately. It is a lot easier to use, portable across >> multiple >> environment including Windows and Linux, and can maintain >> dependencies >> automatically (at least most of them). It also natively uses >> the >> compiler, linker and other tools to build the application(s). >> >> http://www.cmake.org/ >> >> There are some other build environments available but CMake >> appears to >> be the most used and is free to download and use. >> >> What do you think? >> >> David Ashley >> >> >> ------------------------------------------------------------------------------ >> Start Your Social Network Today - Download eXo Platform >> Build your Enterprise Intranet with eXo Platform Software >> Java Based Open Source Intranet - Social, Extensible, Cloud >> Ready >> Get Started Now And Turn Your Intranet Into A Collaboration >> Platform >> http://p.sf.net/sfu/ExoPlatform >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> >> >> ------------------------------------------------------------------------------ >> Start Your Social Network Today - Download eXo Platform >> Build your Enterprise Intranet with eXo Platform Software >> Java Based Open Source Intranet - Social, Extensible, Cloud Ready >> Get Started Now And Turn Your Intranet Into A Collaboration Platform >> http://p.sf.net/sfu/ExoPlatform >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel |
From: René J. <rvj...@xs...> - 2014-04-21 16:46:41
|
and I read that it can generate standard makefiles ... so that might also help. René. On 21 apr. 2014, at 18:28, David Ashley <w.d...@gm...> wrote: > It is available for > > Linux x86 > Mac OSX > Windows > AIX > IRIX > > Most Linux distribution provide via their repositories. The source is > also available for building it on other platforms. > > David Ashley > > On Mon, 2014-04-21 at 12:16 -0400, Rick McGuire wrote: >> I certainly have no particular ties to autotools. My only >> reservations about switching to something else would be to ensure it >> is ubiquitous enough. For example, would cmake be available for >> environments such as z-linux or AIX? >> >> >> Rick >> >> >> On Mon, Apr 21, 2014 at 12:11 PM, David Ashley >> <w.d...@gm...> wrote: >> Ok, new train of thought, same subject. >> >> What about eliminating aototools completely? There are other, >> more >> portable build environments available these days. CMake >> springs to mind >> immediately. It is a lot easier to use, portable across >> multiple >> environment including Windows and Linux, and can maintain >> dependencies >> automatically (at least most of them). It also natively uses >> the >> compiler, linker and other tools to build the application(s). >> >> http://www.cmake.org/ >> >> There are some other build environments available but CMake >> appears to >> be the most used and is free to download and use. >> >> What do you think? >> >> David Ashley >> >> >> ------------------------------------------------------------------------------ >> Start Your Social Network Today - Download eXo Platform >> Build your Enterprise Intranet with eXo Platform Software >> Java Based Open Source Intranet - Social, Extensible, Cloud >> Ready >> Get Started Now And Turn Your Intranet Into A Collaboration >> Platform >> http://p.sf.net/sfu/ExoPlatform >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> >> >> ------------------------------------------------------------------------------ >> Start Your Social Network Today - Download eXo Platform >> Build your Enterprise Intranet with eXo Platform Software >> Java Based Open Source Intranet - Social, Extensible, Cloud Ready >> Get Started Now And Turn Your Intranet Into A Collaboration Platform >> http://p.sf.net/sfu/ExoPlatform >> _______________________________________________ >> Oorexx-devel mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > ------------------------------------------------------------------------------ > Start Your Social Network Today - Download eXo Platform > Build your Enterprise Intranet with eXo Platform Software > Java Based Open Source Intranet - Social, Extensible, Cloud Ready > Get Started Now And Turn Your Intranet Into A Collaboration Platform > http://p.sf.net/sfu/ExoPlatform > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel |