Willy Sudiarto Raharjo wrote:
I am not sure whether your binary is able to run on every Windows machine but your
build > machine even though the build process finishes successfully.
What do you mean by this?
is it because i compile it in cygwin?
Maybe no.
That comes from what is a header file.
A header file, in general, describes what functions are included
in a corresponding library file (.dll).
That implies that if some source codes require one header file at
compilation stage, the source codes also demand its library file
at link and/or run stage.
Don't you think so?
IMHO, using 'stlport' of OOo is the simplest, easiest way
since such library files are included in an installer of OOo.
Indeed, but i ran into trouble when using the stlport from OOo
It couldn't find the include file ctime, so i tried the other ways to
skip the stlport and i got stumbled on the soltools :(
The header file 'ctime' can be found in the folder of the compiler.
$ ls c:/Program\ Files/Microsoft\ Visual\ Studio\ .NET\ 2003/Vc7/include/ctime
It also can be found in the folder of 'stlport'
$ ls $SRC_ROOT/stlport/$INPATH/misc/build/STLport-4.5/stlport/ctime
1. Could you show us parameters given to config_office/configure ?
2. Could you show us some portions of the error messages during
compilation of the module 'stlport'?
$ cd $SRC_ROOT/stlport
$ (date; time build.pl -- PRODUCT=full ; date ) 2>&1 | tee build_`date
+%Y%m%d_%H%M`.log
Caio,
Tora
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
