and I read that it can generate standard makefiles ... so that might also help.
René.
On 21 apr. 2014, at 18:28, David Ashley wrote:
> It is available for
>
> Linux x86
> Mac OSX
> Windows
> AIX
> IRIX
>
> Most Linux distribution provide via their repositories. The source is
> also available
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 wrote:
> It is available for
>
> Linux x86
> Mac OSX
> Windows
> AIX
> IRIX
>
> Most Linux distribution provide via their repositories.
Sounds doable to me.
Rick
On Mon, Apr 21, 2014 at 12:28 PM, David Ashley 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
>
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.
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 wrote:
> Ok,
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 maint
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 th
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 L
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 wrote:
> David Ashley wrote:
> > Of course, the primary problem with using autotools is that Cygwin is a
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
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 wrote:
> I would like to give the autotools on Windows ano
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 overco
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 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
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
proc
14 matches
Mail list logo
