| |
|
| Classification: |
C++ |
Category: |
Utilities & Build Tools |
| Created: |
01/24/2001 |
Modified: |
08/24/2001 |
| Number: |
FAQ-0563 |
| Platform: |
ER5 |
|
Question:
Invoking dlltool from the command line, using an existing path (./build/arm), the dlltool changes the path to tbuild/arm
(prefix 't') and is unable to write to this new non-existing directory. If this new directory is created, dlltool runs.
Where does this extra 't' come from ?
>S:/epoc32/Gcc/Bin/dlltool --output-lib build/arm/kvm.lib --def build/arm/kvm.def --dllname build/arm/kvm[00000002].dll --output-exp
build\kvm.exp --base-file build/arm/kvm.bas ../../../Epoc32/EPOC32/Release/MARM/Deb/edll.o build/arm/kvm.in ../../../Epoc32/EPOC32/Release/MARM/Deb/euser.lib
../../../Epoc32/EPOC32/Release/MARM/Deb/estlib.lib ../../../Epoc32/EPOC32/Release/MARM/Deb/esock.lib ../../../Epoc32/EPOC32/Release/MARM/Deb/insock.lib
../../../Epoc 32/EPOC32/Release/MARM/Deb/libgcc.a
S:/epoc32/Gcc/Bin/dlltool: Unable to open output file tbuild/kvm.exp
Answer:
It is a known deficiency of dlltool that it only allows you to create a .exp file in the current directory. Symbian's Perl
script (Cl_arm.pm in \epoc32\tools\) which invokes dlltool, always creates the .exp file in the current directory as a work
around for this problem. If you want to use dlltool from the command line, you should do the same.
This has been fixed for v6.0 of the Symbian Platform.
|
| |
|
![[Index]](../../a_stock/btn_index_wt.gif){kind=small}
![[spacer]](../../a_stock/btn_spacer.gif){kind=small}
![[Previous]](../../a_stock/btn_prev_wt.gif){kind=small}
![[Next]](../../a_stock/btn_next_wt.gif){kind=small}
![[Previous]](../../a_stock/btn_prev.gif){kind=small}
![[Top]](../../a_stock/btn_top.gif)
![[Next]](../../a_stock/btn_next.gif){kind=small}