Hi,
I've just posted a status update for our build environment effort to the
global dev list. I think this is a more appropriate list for that, as I
want to reach more people than usually hang around on this list. ;-)
So please follow up in the global dev list.
Best regards,
Mathias
--
On Wed, Feb 3, 2010 at 4:43 PM, Mathias Bauer nospamfor...@gmx.de wrote:
I hope that by investigating the makefiles of the modules at the top of
the table we can identify the dark magic Björn has mentioned.
According to a cursory look most of those seem to be of the type call
some command with
On 02/03/10 15:38, Mathias Bauer wrote:
I tend to agree that - whatever we will do - we probably won't get rid
of cygwin. Where we have to get rid of it is the building of the
normal modules.
As an example, if a developer is going to work on sw, he might want to
build sw and all c++ libraries
Thorsten Behrens wrote:
The story on win32 (and other, not-so-standard platforms I believe
you alluded to) is totally different, of course, but you won't fix
that by prohibiting sed awk - fixing the root cause here means
performing cross-compilation for those platforms.
(you need to
Mathias Bauer wrote:
I just wanted to point out that you seem to underestimate the value
of a less diverse build system. Most probably because you don't
have to maintain it. ;-)
Quite the contrary. I have to personally setup all the win32 build
prerequisites on each and every box or vm I
On 02/02/10 10:05, Jussi Pakkanen wrote:
Another point is However, there are many cases where the current
build process depends on a large set of external tools like bash, awk,
findutils, coreutils. Does the actual building require these or is it
more of a case of need these, because
On Tue, 02 Feb 2010 11:05:26 +0200
Jussi Pakkanen jpakk...@gmail.com wrote:
There are some inconsistencies with the page. I'll post them here
rather than directly to the page to prevent an editing war.
Firstly under dependencies it says [CMake] is not usually available
on the default
On Tue, Feb 2, 2010 at 1:08 PM, bjoern michaelsen - Sun Microsystems -
Hamburg Germany bjoern.michael...@sun.com wrote:
Firstly under dependencies it says [CMake] is not usually available
on the default install of many platforms. and then a bit further down
One might consider using Python as a
On Tue, 02 Feb 2010 16:21:24 +0200
Jussi Pakkanen jpakk...@gmail.com wrote:
No I did not, but despite that it somewhat harsh to imply that CMake
is hard to get or install. Getting it is roughly as hard as getting a
compiler (buying full registered versions of MSVC notwithstanding).
On
Thorsten Behrens wrote:
bjoern michaelsen - Sun Microsystems - Hamburg Germany wrote:
I started a new wikipage here:
http://wiki.services.openoffice.org/wiki/Build_Environment_Effort/New_Build_System_Requirements
collecting the major requirements for a new build system and what needs
to be
Jussi Pakkanen wrote:
Another point is However, there are many cases where the current
build process depends on a large set of external tools like bash, awk,
findutils, coreutils. Does the actual building require these or is it
more of a case of need these, because dmake/build.pl needs these?
Hi List,
I started a new wikipage here:
http://wiki.services.openoffice.org/wiki/Build_Environment_Effort/New_Build_System_Requirements
collecting the major requirements for a new build system and what needs
to be done to implement these requirements with GNU make and CMake
(those two currently
bjoern michaelsen - Sun Microsystems - Hamburg Germany wrote:
I started a new wikipage here:
http://wiki.services.openoffice.org/wiki/Build_Environment_Effort/New_Build_System_Requirements
collecting the major requirements for a new build system and what needs
to be done to implement these
13 matches
Mail list logo
