On 08/08/2015 Jason Marshall wrote:
build completed and I was able to install from the build. ...
Hopefully from there I can tackle some of the smaller issues
identified on Bugzilla and so make a meaningful contribution.
Welcome Jason, congratulations and if you want to start making some
small
Hi Jason,
Jason Marshall schrieb:
Hi Regina
Thank you for the advice here. I followed what you said and moved
the source into the root of C drive, placing it in a directory with
no special characters. I did subsequently encounter an issue with
building the modules associated with the SDK, bu
Hi Regina
Thank you for the advice here. I followed what you said and moved the source
into the root of C drive, placing it in a directory with no special characters.
I did subsequently encounter an issue with building the modules associated
with the SDK, but I re-ran configure with SDK disa
Hi Jason,
Jason Marshall schrieb:
Hi Regina
Thank you for looking at this. I have ensured that with a new Cygwin
session I have run the following successfully:
/source winenv.set.sh/
Following that, I have run the following:
/build --all:comphelper 2>&1 | tee mybuild.log/
The bui
03:11 +0200
> From: rb.hensc...@t-online.de
> To: dev@openoffice.apache.org
> Subject: Re: Build Problem
>
> Hi Jason,
>
> you have put the source into a folder under "tmp". I see the same in the
> mail you referred. I'm not sure, but it might be, that this confuses
&g
y that is not
temp? If so, would this simply be to the root of the Cygwin file system?
If you require any further information, please do let me know.
Thanks again.
Jason
> Date: Sat, 18 Jul 2015 20:03:11 +0200
> From: rb.hensc...@t-online.de
> To: dev@openoffice.apache.org
>
Hi Jason,
you have put the source into a folder under "tmp". I see the same in the
mail you referred. I'm not sure, but it might be, that this confuses
some path settings.
Some curious errors appear, if the path settings are not applied or if
build is called from a wrong directory.
Please
On Fri, Jul 5, 2013 at 10:11 AM, Kay Schenk wrote:
>
>
> On Fri, Jul 5, 2013 at 9:02 AM, Herbert Duerr wrote:
>
>> On 05.07.2013 17:53, Kay Schenk wrote:
>>
>>> I'm trying to a build and seem to be missing oox/source/token/tokens.hxx
>>>
>>> referenced in oox/prj/d.lst
>>>
>>> I seem to have oo
On Fri, Jul 5, 2013 at 9:02 AM, Herbert Duerr wrote:
> On 05.07.2013 17:53, Kay Schenk wrote:
>
>> I'm trying to a build and seem to be missing oox/source/token/tokens.hxx
>>
>> referenced in oox/prj/d.lst
>>
>> I seem to have oox/source/token/tokens.hxx.**head and
>> oox/source/token/tokens.hxx
On 05.07.2013 17:53, Kay Schenk wrote:
I'm trying to a build and seem to be missing oox/source/token/tokens.hxx
referenced in oox/prj/d.lst
I seem to have oox/source/token/tokens.hxx.head and
oox/source/token/tokens.hxx.tail
but no oox/source/token/tokens.hxx.
Can d.lst be fixed to use these
Am 31.05.13 08:59, schrieb Herbert Dürr:
Hi Raphael,
On 2013/05/30 8:27 PM, Raphael Bircher wrote:
Mac OS X 10.7 with XCode 4.3
My build stops at the epm modul. I know there is a workflow to find more
details about the breaker, but I fergot it :-( Can sameone help me?
Go into the module that
Hi Raphael,
On 2013/05/30 8:27 PM, Raphael Bircher wrote:
Mac OS X 10.7 with XCode 4.3
My build stops at the epm modul. I know there is a workflow to find more
details about the breaker, but I fergot it :-( Can sameone help me?
Go into the module that had the problem and run
build verbose=
Hi guys,
I have some problems building ( see below).
The guide I've used is the one at :
http://wiki.openoffice.org/wiki/User:Dyrcona/LeopardBuild#flex
The output I get after the following command : build --from l10ntools -P4
--dlv_switch -link
is :
BUILD FAILED
/Users/maartenkesselaers/Docum
I'm building the total source in the terminal, not with Eclipse.
The building guide that I used was the normal one for Mac OS X Snow Leopard.
I haven't changed any classpath in my Java build env.
Regards,
Maarten
Op 15-feb.-2013 09:32 schreef "Jürgen Schmidt" het
volgende:
> On 2/15/13 7:00 AM,
On 2/15/13 7:00 AM, Maarten Kesselaers wrote:
> I have full working eclipse env and try to build on Mac OS X 10.6.
> All prerequisits are installed as described in the guide.
l10tools is normally build as all other modules in a command line
environment triggered via makefiles. I am not aware that
I have full working eclipse env and try to build on Mac OS X 10.6.
All prerequisits are installed as described in the guide.
Thanks,
Maarten
Op 14-feb.-2013 09:33 schreef "Jürgen Schmidt" het
volgende:
> On 2/13/13 10:27 PM, Maarten Kesselaers wrote:
> > My build just crashed on the build.xml un
On 2/13/13 10:27 PM, Maarten Kesselaers wrote:
> My build just crashed on the build.xml under
> ./main/l10ntools/java/jpropex/ at line 122 :
>
> 122classpathref="classpath">
>
> So I guess I need to set a CLASSPATH, right?
> To which directory should it be set?
>
do you have con
Welcome!
2013/1/21 2
> Fan Zheng，
> I'm so sorry for missing your reply because of my job. I have
> finished the building with your help.
> Thank you!
>
> Yi
> At 2013-01-11 15:07:44,"Fan Zheng" wrote:
> >Seems your cygwin did not to be allow to use system api to create process.
> >Did
Fan Zheng，
I'm so sorry for missing your reply because of my job. I have finished
the building with your help.
Thank you!
Yi
At 2013-01-11 15:07:44,"Fan Zheng" wrote:
>Seems your cygwin did not to be allow to use system api to create process.
>Did you use some kind of anti-virus applic
Seems your cygwin did not to be allow to use system api to create process.
Did you use some kind of anti-virus application like Symantec EndPoint
Protection? If yes, you may need to install a newly version with certain
verification for cygwin.
BTW, the method you executed last one "make -sr" will
After my step 2, I go to sw and run "build debug=true", but it didn'i work. I
got the message:
>/cygdrive/d/aoo/main/sw
>$ build debug=true
cygwin warning:
MS-DOS style path detected: D:/aoo/main/solenv/bin/build.pl
Preferred POSIX equivalent is: /cygdrive/d/aoo/main/solenv/bin/build.pl
CYG
I am not sure your step 4,5,6...After your step 2, you can go to sw module
and run "build debug=true" to do individual build with debug info once you
have done modifications in sw module,and then you will find
that breakpoints can be added to your modified files after the new built
dlls at ..\main\
Sure,the compiled object files can be found at ..\main\solver\350\
wntmsci12.pro\workdir\CxxObject\sw\.,and dlls can be got
from ..\main\solver\350\wntmsci12.pro\workdir\LinkTarget\Library..Thanks.
On Wed, Jan 9, 2013 at 3:52 PM, Herbert Duerr wrote:
> On 09.01.2013 08:06, 2 wrote:
>
>> whe
On 09.01.2013 08:06, 2 wrote:
when got my own build, I couldn't found the filefolder wntmsci12.pro in sw
module which be found in sc module, could it be said that my build failed ?
That is no problem: The sw module has been converted to gbuild, so that
the files are now in main/solver/35
24 matches
Mail list logo
