Volker Quetschke wrote:
[...]
Hamburg uses [...] 4nt for Windows builds of OOo.
The community uses bash[*] for all OOo builds and discourages the use
of 4nt. This frequently leads to broken milestones for the community
that seem to build fine and are OKed by RE and QA.
That is a known
Hello,
Hamburg uses [...] 4nt for Windows builds of OOo.
4nt is used also to drive the OS/2 build system; it is named 4os2 here
(and is open source software), but OS/2 scripts uses '4nt' to be
compatible with existing makefiles.
Bye,
Yuri Dario
/*
* member of TeamOS/2 - Italy
*
Yuri Dario wrote:
Hello,
Hamburg uses [...] 4nt for Windows builds of OOo.
4nt is used also to drive the OS/2 build system; it is named 4os2 here
(and is open source software), but OS/2 scripts uses '4nt' to be
compatible with existing makefiles.
Well, for W32 builds both bash and 4nt
Yuri Dario wrote:
Hi Volker,
free software. I thought your OS/2 environment is unix-like? Did you
ever try to use USE_SHELL=bash?
when I started porting, the only shell choices were tcsh and 4nt; since
the first one was not available and porting it was not simple, I used
4nt/4os2 because
Jan Holesovsky wrote:
Hi Ruediger,
I am sorry, I missed a part of the mail when I was answering previously :-(
No problem.
On Monday 08 October 2007 17:36, Rüdiger Timm wrote:
This would tremendously decrease the learning curve for the new
developers as well. Imagine someone who wants
Rüdiger Timm wrote:
Personally, I do not like spitting up sources at all. But that's my very
personal opinion.
Splitting up source definitely is a good idea. Maybe not for people
building everything anyway but it would be a huge step ahead for the
casual developer like volunteers, distro
