help with windows tinbuild and symlinks

[Noel Grandin]

On 2012-05-03 13:30, Michael Stahl wrote:
> the attachment contains an utterly horrible workaround that you could 
> try out, 

With your patch, if I specify the path cygwin style, it fails very quickly.

If I specify the path as "D:\" it gets much further but then fails in 
the bridges module.

Both error logs attached.





Disclaimer: http://www.peralex.com/disclaimer.html


-------------- next part --------------
log for /cygdrive/c/LibreOffice/libo/boost
cd ./wntmsci12.pro/misc/build/boost_1_44_0/libs/thread/src/win32 && dmake -P15 
cd ./wntmsci12.pro/misc/build/boost_1_44_0/libs/date_time/src/gregorian && dmake -P15 
/cygdrive/c/LibreOffice/libo/solenv/wntmsci12/bin/dmake.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory
/cygdrive/c/LibreOffice/libo/solenv/wntmsci12/bin/dmake.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory
dmake:  Error code 127, while making 'boostdatetimelib'
Killing of pid 3888 from pq[0] failed with: No such process - 15 ret: -1
log for /cygdrive/c/LibreOffice/libo/boost
cd ./wntmsci12.pro/misc/build/boost_1_44_0/libs/thread/src/win32 && dmake -P15 
cd ./wntmsci12.pro/misc/build/boost_1_44_0/libs/date_time/src/gregorian && dmake -P15 
/cygdrive/c/LibreOffice/libo/solenv/wntmsci12/bin/dmake.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory
dmake:  Error code 127, while making 'boostthreadlib'
-------------- next part --------------
log for /cygdrive/c/LibreOffice/libo/bridges/unotypes
cppumaker.exe : init registries failed, check your registry files.
dmake:  Error code 99, while making '../wntmsci12.pro/inc/unotypes_headergen.done'
log for /cygdrive/c/LibreOffice/libo/bridges/unotypes
cppumaker.exe : init registries failed, check your registry files.
dmake:  Error code 99, while making '../wntmsci12.pro/inc/unotypes_headergen.done'
log for /cygdrive/c/LibreOffice/libo/remotebridges/source/unourl_resolver
D:\solver\wntmsci12.pro\bin\rdbmaker.exe : init registries failed, check your registry files.
dmake:  Error code 99, while making '../../wntmsci12.pro/bin/uuresolver.rdb'

using: cppumaker.exe [-options] file_1 ... file_n
Options:
    -O<path>   = path describes the root directory for the generated output.
                 The output directory tree is generated under this directory.
    -T<name>   = name specifies a type or a list of types. The output for this
      [t1;...]   type is generated. If no '-T' option is specified,
                 then output for all types is generated.
                 Example: 'com.sun.star.uno.XInterface' is a valid type.
    -B<name>   = name specifies the base node. All types are searched under this
                 node. Default is the root '/' of the registry files.
    -L         = UNO type functions are generated lightweight, that means only
                 the name and typeclass are given and everything else is retrieved
                 from the type library dynamically. The default is that UNO type
                 functions provides enough type information for boostrapping C++.
                 '-L' should be the default for external components.
    -C         = UNO type functions are generated comprehensive that means all
                 necessary information is available for bridging the type in UNO.
    -G         = generate only target files which does not exists.
    -Gc        = generate only target files which content will be changed.
    -X<file>   = extra types which will not be taken into account for generation.

cppumaker.exe Version 2.0

log for /cygdrive/c/LibreOffice/libo/remotebridges/source/unourl_resolver
Making:    module definition file uuresolver.uno.def
D:\solver\wntmsci12.pro\bin\rdbmaker.exe : init registries failed, check your registry files.
dmake:  Error code 99, while making '../../wntmsci12.pro/bin/uuresolver.rdb'

using: cppumaker.exe [-options] file_1 ... file_n
Options:
    -O<path>   = path describes the root directory for the generated output.
                 The output directory tree is generated under this directory.
    -T<name>   = name specifies a type or a list of types. The output for this
      [t1;...]   type is generated. If no '-T' option is specified,
                 then output for all types is generated.
                 Example: 'com.sun.star.uno.XInterface' is a valid type.
    -B<name>   = name specifies the base node. All types are searched under this
                 node. Default is the root '/' of the registry files.
    -L         = UNO type functions are generated lightweight, that means only
                 the name and typeclass are given and everything else is retrieved
                 from the type library dynamically. The default is that UNO type
                 functions provides enough type information for boostrapping C++.
                 '-L' should be the default for external components.
    -C         = UNO type functions are generated comprehensive that means all
                 necessary information is available for bridging the type in UNO.
    -G         = generate only target files which does not exists.
    -Gc        = generate only target files which content will be changed.
    -X<file>   = extra types which will not be taken into account for generation.

cppumaker.exe Version 2.0