hi!
On 06/16/10 11:25, Michael Stahl wrote:
On 15/06/2010 17:54, Davide Dozza wrote:
Davide Dozza ha scritto:
[...]
Making:items.srs
cpp: line 0, Error: Too many file arguments. Usage: cpp [input [output]]
Error starting preprocessor
dmake: Error code 1, while making '../../wntmsci12.p
hi!
Stephan Bergmann wrote:
On 01/28/10 19:14, Stephan Bergmann wrote:
On 01/28/10 18:26, Hans-Joachim Lankenau - Sun Microsystems Germany
wrote:
hi!
since the external source tarballs (e.g. boost/download/*) add their
size to the repository each time a new version is committed, it's o
-Joachim Lankenau - Sun Microsystems Germany
wrote:
hi!
since the external source tarballs (e.g. boost/download/*) add their
size to the repository each time a new version is committed, it's one of
the major sources of the growth of the repository.
the cws ause110 implements a different approa
hi!
since the external source tarballs (e.g. boost/download/*) add their
size to the repository each time a new version is committed, it's one of
the major sources of the growth of the repository.
the cws ause110 implements a different approach to deal with these large
binary files:
- a file na
hi!
i'm sorry to announce that dropping 4nt support has to be postponed by
about four weeks.
tschau...
ause
Hans-Joachim Lankenau - Sun Microsystems Germany wrote:
hi!
i'm not sure if anyone still tries to use 4nt in an OOo environment, so
just in case...
the CWS kick4nt w
hi!
i'm not sure if anyone still tries to use 4nt in an OOo environment, so
just in case...
the CWS kick4nt will remove 4nt support in the module solenv (other CWS
will follow...). the integration of that CWS is planned for DEV300_m54.
tschau...
ause
--
hi!
for those of you who are building extensions in the OOo/SO environment,
the following link could be of interest:
http://wiki.services.openoffice.org/wiki/Extensions_packing
beginning with DEV300_m18 the makefiles in
reportdesign/util
filter/source/pdfimport
sdext/source/minimizer
show the
hi!
the to be integrated CWS ause090 should reduce the pain of dealing with
patches to external modules a bit.
- on several requests (see comments in the issues of that CWS), i
switched the generated output format of "dmake create_patch" to be a
unified diff.
- i also inserted the very usefull "
hi!
Stephan Bergmann wrote:
> Hans-Joachim Lankenau wrote:
>> hi!
>>
>> with the integration of CWS ause085 into SRC680_m243 the reworked
>> dependency generation for c/c++ files will hit the main codeline.
>>
>> if you build with "nodep=true"
hi!
with the integration of CWS ause085 into SRC680_m243 the reworked
dependency generation for c/c++ files will hit the main codeline.
if you build with "nodep=true" or don't do incremental builds at all,
you may stop reading here...
the most visible change will be that dependencies are only ge
hi!
when sharing a tree (source and solver), you can make a local copy of a
module and work on it, using all of the shared tree as prerequsite
without messing up the shared tree for others.
tschau...
ause
Oliver Braun wrote:
> Hi *,
>
> Thorsten Behrens wrote:
>> Stephan Bergmann <[EMAIL PROTE
hi!
i picked that patch and did some builds with the resulting ccache.
first of all, great work! i didn't ecounter even one problem with the
ccache on windows. it's seamless plug and play (except that you should
raise the max cache size - 2GB could be a nice number). it even works in
SO/4nt envir
hi!
how was this source tree created? looks like there are modules missing.
tschau...
ause
Classic Kai wrote:
> I am building OOF680_m17 in my Windows XP as well.
>
> I do the following:
> SRC> cd config_office
> SRC/config_office> ./configure --disable-build-mozilla
> --with-ant-home=/cygdri
hi!
looks like the typical "tcsh-hang".
(http://wiki.services.openoffice.org/wiki/Special:Search?search=tcsh+bash&go=Go)
try "--with-use-shell=bash" instead.
tschau...
ause
Classic Kai wrote:
> Recent stops at jurt module:
> /cygdrive/d/OO2.2.0/OOF680_m14/jurt/util
> dmake: Executing shell mac
hi!
looks like the typical "tcsh-hang".
(http://wiki.services.openoffice.org/wiki/Special:Search?search=tcsh+bash&go=Go)
try "--with-use-shell=bash" instead.
tschau...
ause
Classic Kai wrote:
> Recent stops at jurt module:
> /cygdrive/d/OO2.2.0/OOF680_m14/jurt/util
> dmake: Executing shell mac
hi!
a possible way to solve such kind of conflics is to define different
output directories.
in your case this could be achieved by e.g.
SLO+:!=$(SLO)$/$(wherever_you_got_intel_and_powerpc)
RSLO+:!=$(RSLO)$/$(wherever_you_got_intel_and_powerpc)
in the local makefile and using plain SLO for the
hi!
i did play with it a bit but left scons aside.
after a few tests i kicked out gnumake aswell as it used up all memory
on my machine and started swapping...
also i noticed that dmake 4.5 and dmake 4.6 make a huge difference.
running run_test.sh on a local disk:
complete
hi!
i was playing now for several days with the prototype of the jam
buildsystem and i would like to share my findings up to now.
the main thing i've learned, is to have a look at the build output
instead of being focused on buildtimes only. more on this later...
all numbers in this text are fro
hi!
just checked, you're right! now i _am_ surprised. must have missed this
completely
tschau...
ause
Stephan Bergmann wrote:
> Frank Schönheit - Sun Microsystems Germany wrote:
>> Hi Ause,
>>
>>
So, if in an OOo build, I touch svx/inc/svxids.hrc and deliver it, then
all depending fil
hi!
Frank Schönheit - Sun Microsystems Germany wrote:
> Hi Kai,
>
>> This objection seems to come up now and then, so I wanted to make sure
>> we are talking about the same kind of full program dependencies.
>> ...
>>
>> Now, if sw depends on svx/inc/svxids.hrc everything along that path will
hi!
AFAIK, there is no easy way to add this to the build system in a clean way.
for windows like library names you may try adding something like
$(SHLnDEPN) : $(SHLn$(foreach,i,$(SHLnSTDLIBS) $(SOLARLIBDIR)$/$i)
somewhere in _tg_shl.mk/tg_shl.mk
another workaround could be using the "killbin
hi!
see #i52789#
tschau...
ause
Hristo Simenov Hristov wrote:
> On Tuesday 11 October 2005 11:59, Hristo Simenov Hristov wrote:
>>On Tuesday 11 October 2005 09:55, Hristo Simenov Hristov wrote:
>>>On Monday 10 October 2005 18:28, Hristo Simenov Hristov wrote:
Thanks for help Pavel,
I kn
hi!
there obviously are some problems in the current cygwin1.dll.
until now (snapshot 20050828) each new snapshot produced less hangs.
a temporary workaround here was to remove the -f flag for subshells in
"solenv/inc/startup/wnt/macros.mk" which on the other hand slows down
the build dramatical
hi!
as i learned that this isn't an uncommon use, improved makefiles can be
found on CWS "debsize".
tschau...
ause
Hans-Joachim Lankenau wrote:
> hi!
>
> packing more than one languages is an unexpected use as you'll loose
> correct dependencies on other targe
hi!
packing more than one languages is an unexpected use as you'll loose
correct dependencies on other targets in this makefile.
anyway it still works as "good" as before when using
dmake openoffice_pl_en-US.rpm
or the according line for you build
tschau...
ause
ps: i wasn't even aware that
hi!
hmm.. you should first decide if you want to build with msvc-toolkit (MS
compiler) _or_ mingw (gcc).
mixing both doesn't make sense to me.
tschau...
ause
Ajoy Thamattoor wrote:
> On 8/19/05, Hans-Joachim Lankenau <[EMAIL PROTECTED]> wrote:
>>hi!
>>
>>APP1L
hi!
APP1LINKER is set to the value of the variable LINK/LINKC which
orginates from "solenv/inc/wnt.mk".
i would suspect the MSC compiler detection as source of your problem but
there should be hints in the config.log..
as always, some additional information would avoid too much guessing:
- miles
hi!
maybe #i51097# is similar?
tschau...
ause
Alan Yaniger wrote:
Hi list,
I'm doing my first 2.0 beta Windows build, on the m113 code, using
Windows XP Professional. I started out using 1.5.18 of the cygwin dll.
After I ran configure and bootstrap, succesfully, I would run dmake, and
it
hi!
right, there were several issues in the past with empty lines inside
rule/target definition. IIRC, sometimes related to lineend conventions.
also new (not yet in the MWS) versions seem to be able to handle this
correct.
this error exactly looks like.
anyway, i would suggest removing the
hi!
in
"solenv/inc/startup/wnt"
do
cvs update -r1.15 macros.mk
should do the trick.
tschau...
ause
[EMAIL PROTECTED] wrote:
Now, we are getting somewhere.
My CVS client insists on bringing down version 1.14
Is it possible this is a recent fix and CVS hasn't updated
itself yet?
Could someo
hi!
"solenv/inc/startup/wnt/macros.mk" is the file that needs update:
revision 1.15
date: 2005/07/13 17:00:14; author: hjs; state: Exp; lines: +1 -1
#i1# fix global win/tcsh breaker
and yes, i did break it :-(
tschau...
ause
[
hi!
have a look at issue i46971. the applied patch should help
tschau...
ause
dwb wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joey,
Joey Stanford wrote:
| 2nd request for assistance
|>> Any ideas why tg_compv.mk does like GCC 3.3.5?
|>> =
|>> Building project beanshell
|>>
hi!
make sure to cleanup your local output tree (e.g. extras/unxlngi6.pro).
your error looks like remaining dependency files (*.dpz*) from a
previous build.
tschau...
ause
dwb wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm trying to build m103 under Linux and get the following error wh
hi!
in the directory "svtools" try "cvs update -rSRC680_m102 -d" to fetch
directories not yet existing.
tschau...
ause
Cornel Plochowietz wrote:
Hi,
Building SRC680_m102 I get: ERROR: svtools/source/productregistration not
found!!
I could'nt find it in cvs. Can anyone tell me where I get it?
hi!
make sure to have populated "helpcontent2/source/auxiliary/en-GB". note
that in m79 or newer there had been a change of the content so you might
want to update.
last but not least, try "dev@l10n.openoffice.org" for localization
related questions.
tschau...
ause
David wrote:
Dear all,
I am t
:
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Hans-Joachim Lankenau) wrote:
hi!
"cvs checkout" should have created a directory "vos/util/defs". that's
where this tool (ldump) wants to write its output. if this directory
doesn't exist or isn't wr
hi!
"cvs checkout" should have created a directory "vos/util/defs". that's
where this tool (ldump) wants to write its output. if this directory
doesn't exist or isn't writeable, you'll get this error.
tschau...
ause
Richard Gadsden wrote:
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Richa
37 matches
Mail list logo