Skip to main content

integration of phoneME with a custom library

14 replies [Last post]
paolopaolo
Offline
Joined: 2008-01-03
Points: 0

hi,

we sucessfully compiled and ran the phoneME: our build architecture is linux i386 and the target platform is linux_arm_gcc.
Now, we are trying to modify the phoneME source code to invoke a function that has been defined in a custom library we developed.
This function should be invoked at initialization time, i.e. among the first operations that the phomeME performs.
We chose to insert this invocation in the file JVM.cpp under the directory $MEHOME/cldc/src/vm/share/runtime .
Moreover, we should modify some makefiles to include the options to find our library.
Supposing that all the stuff of our library are under the $OUR_LIB directory, and that the library name is libOurLib.so, we think we shoud insert in a cldc makefile the option
-I $OUR_LIB
when compiling and the options
-L $OUR_LIB -lOurLib
when linking.

Is it the right procedure?

We tryied to do it modifying the jvm.make file under the directory $MEHOME/cldc/build/share and we added the line
-I $OUR_LIB
to the CPP_INCLUDE_DIRS variable and the line
-L $OUR_LIB -lOurLib
to the LINK_FLAGS variable.

However, this return us an error when compiling the cldc.
In particular, if we use the libOurLib.so that has been compiled for arm, we get the following error:
--------------------------------------------------------------------------------------------------------------------------------
linking ASM loop generator: ../../loopgen/app/loopgen
/usr/bin/ld: skipping incompatible /home/user/libOurLib.so when searching for -lOurLib
(where /home/user/ is $OUR_LIB)
--------------------------------------------------------------------------------------------------------------------------------
hence we tried to use the libOurLib.so that has been compiled for i386, we didn't get the previous error but we get the following one at a later stage of the compilation:
-------------------------------------------------------------------------------------------------------------------------------
generating CPU stubs /home/user/phoneme_feature/cldc/src/vm/cpu/c/AsmStubs_i386.s
...OopMapsSkeleton.cpp
../../loopgen/app/loopgen: error while loading shared libraries libOurLib.so: cannot open shared object file: no such file or directory
---------------------------------------------------------------------------------------------------------------------------------

How can we add an invocation to a custom library in the cldc source code and compile the cldc?

Any suggestion will be appreciated.
Sorry for the long post, thanks a lot.
paolo.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
gammy
Offline
Joined: 2008-01-08
Points: 0

Hi danila,

i am building CLDC on ARM and i am getting following error can u help me to solve this error.whole process while building=>

==============================

creating build tools...

==============================

make[1]: Entering directory `/home/phoneme_feature/build_output/cldc/
linux_arm_926/tools'

Note: Some input files use or override a deprecated API.

Note: Recompile with -deprecation for details.

created jcc.jar

created buildtool.jar

make[1]: Leaving directory `/home/phoneme_feature/build_output/cldc/
linux_arm_926/tools'

done

Finding .java files ...

done

created /home/phoneme_feature/build_output/cldc/linux_arm_926/loopgen/
app/Makefile

==============================

creating ASM loop generator in debug mode

build flags: NO_DEBUG_SYMBOLS=true

==============================

make[1]: Entering directory `/home/phoneme_feature/build_output/cldc/
linux_arm_926/loopgen/app'

generating ../generated/Dependencies ...

reading database: /home/phoneme_feature/cldc/src/vm/includeDB

merging source files, limit = 35

excluded from merging: JarFileUncommon.cpp

excluded from merging: OsFile.cpp

excluded from merging: OsFile_linux.cpp

excluded from merging: OsMemory.cpp

excluded from merging: OsMemory_linux.cpp

excluded from merging: OsMisc_linux.cpp

excluded from merging: OsSocket_linux.cpp

excluded from merging: OS_linux.cpp

excluded from merging: KniUncommon.cpp

excluded from merging: NativesTable.cpp

excluded from merging: FloatSupport_arm.cpp

excluded from merging: ROMImage.cpp

excluded from merging: jvmspi.cpp

excluded from merging: Main_linux.cpp

excluded from merging: BSDSocket.cpp

excluded from merging: PCSLSocket.cpp

excluded from merging: HotRoutines0.cpp

excluded from merging: HotRoutines1.cpp

excluded from merging: ReflectNatives.cpp

writing individual include files ...couldn't find in vpath:
ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: OS.cpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMTools.hpp

couldn't find in vpath: ROMProfile.hpp

couldn't find in vpath: ROMOptimizer.hpp

couldn't find in vpath: ROMWriter.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: SourceROMWriter.hpp

couldn't find in vpath: BinaryROMWriter.hpp

couldn't find in vpath: SegmentedSourceROMWriter.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMTools.hpp

couldn't find in vpath: ROMProfile.hpp

couldn't find in vpath: ROMOptimizer.hpp

couldn't find in vpath: ROMWriter.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: SourceROMWriter.hpp

couldn't find in vpath: BinaryROMWriter.hpp

couldn't find in vpath: BytecodeOptimizer.hpp

couldn't find in vpath: ConstantPoolRewriter.hpp

couldn't find in vpath: ROMStructsWriter.hpp

couldn't find in vpath: ROMWriter.cpp

couldn't find in vpath: SourceObjectWriter.cpp

couldn't find in vpath: SourceROMWriter.cpp

couldn't find in vpath: ROMStructsWriter.cpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMTools.hpp

couldn't find in vpath: ROMTools.cpp

couldn't find in vpath: ROMProfile.hpp

couldn't find in vpath: ROMOptimizer.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: BytecodeOptimizer.hpp

couldn't find in vpath: ConstantPoolRewriter.hpp

couldn't find in vpath: MethodInvocationClosure.hpp

couldn't find in vpath: ROMInliner.hpp

couldn't find in vpath: ROMWriter.hpp

couldn't find in vpath: ROMOptimizer.cpp

couldn't find in vpath: SourceROMOptimizer.cpp

couldn't find in vpath: SourceROMWriter.hpp

couldn't find in vpath: SegmentedSourceROMWriter.hpp

couldn't find in vpath: ROM.cpp

couldn't find in vpath: BinaryROM.cpp

couldn't find in vpath: BinaryROMWriter.hpp

couldn't find in vpath: JVM.cpp

couldn't find in vpath: BytecodeOptimizer.cpp

couldn't find in vpath: ConstantPoolRewriter.cpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: MethodInvocationClosure.hpp

couldn't find in vpath: ROMTools.hpp

couldn't find in vpath: ROMProfile.hpp

couldn't find in vpath: ROMOptimizer.hpp

couldn't find in vpath: MethodInvocationClosure.cpp

couldn't find in vpath: ROMInliner.hpp

couldn't find in vpath: ROMInliner.cpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: ROMWriter.hpp

couldn't find in vpath: ROMProfile.cpp

couldn't find in vpath: SourceROMWriter.hpp

couldn't find in vpath: SegmentedSourceROMWriter.hpp

couldn't find in vpath: SegmentedSourceROMWriter.cpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

done (25 files.)

writing grand include file

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMTools.hpp

couldn't find in vpath: ROMProfile.hpp

couldn't find in vpath: ROMOptimizer.hpp

couldn't find in vpath: ROMWriter.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: SourceROMWriter.hpp

couldn't find in vpath: BinaryROMWriter.hpp

couldn't find in vpath: SegmentedSourceROMWriter.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMTools.hpp

couldn't find in vpath: ROMProfile.hpp

couldn't find in vpath: ROMOptimizer.hpp

couldn't find in vpath: ROMWriter.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: SourceROMWriter.hpp

couldn't find in vpath: BinaryROMWriter.hpp

couldn't find in vpath: BytecodeOptimizer.hpp

couldn't find in vpath: ConstantPoolRewriter.hpp

couldn't find in vpath: ROMStructsWriter.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMTools.hpp

couldn't find in vpath: ROMProfile.hpp

couldn't find in vpath: ROMOptimizer.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: BytecodeOptimizer.hpp

couldn't find in vpath: ConstantPoolRewriter.hpp

couldn't find in vpath: MethodInvocationClosure.hpp

couldn't find in vpath: ROMInliner.hpp

couldn't find in vpath: ROMWriter.hpp

couldn't find in vpath: SourceROMWriter.hpp

couldn't find in vpath: SegmentedSourceROMWriter.hpp

couldn't find in vpath: BinaryROMWriter.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: MethodInvocationClosure.hpp

couldn't find in vpath: ROMTools.hpp

couldn't find in vpath: ROMProfile.hpp

couldn't find in vpath: ROMOptimizer.hpp

couldn't find in vpath: ROMInliner.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: ROMWriter.hpp

couldn't find in vpath: SourceROMWriter.hpp

couldn't find in vpath: SegmentedSourceROMWriter.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

writing dependencies file

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: OS.cpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMTools.hpp

couldn't find in vpath: ROMProfile.hpp

couldn't find in vpath: ROMOptimizer.hpp

couldn't find in vpath: ROMWriter.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: SourceROMWriter.hpp

couldn't find in vpath: BinaryROMWriter.hpp

couldn't find in vpath: SegmentedSourceROMWriter.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMTools.hpp

couldn't find in vpath: ROMProfile.hpp

couldn't find in vpath: ROMOptimizer.hpp

couldn't find in vpath: ROMWriter.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: SourceROMWriter.hpp

couldn't find in vpath: BinaryROMWriter.hpp

couldn't find in vpath: BytecodeOptimizer.hpp

couldn't find in vpath: ConstantPoolRewriter.hpp

couldn't find in vpath: ROMStructsWriter.hpp

couldn't find in vpath: ROMWriter.cpp

couldn't find in vpath: SourceObjectWriter.cpp

couldn't find in vpath: SourceROMWriter.cpp

couldn't find in vpath: ROMStructsWriter.cpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMTools.hpp

couldn't find in vpath: ROMTools.cpp

couldn't find in vpath: ROMProfile.hpp

couldn't find in vpath: ROMOptimizer.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: BytecodeOptimizer.hpp

couldn't find in vpath: ConstantPoolRewriter.hpp

couldn't find in vpath: MethodInvocationClosure.hpp

couldn't find in vpath: ROMInliner.hpp

couldn't find in vpath: ROMWriter.hpp

couldn't find in vpath: ROMOptimizer.cpp

couldn't find in vpath: SourceROMOptimizer.cpp

couldn't find in vpath: SourceROMWriter.hpp

couldn't find in vpath: SegmentedSourceROMWriter.hpp

couldn't find in vpath: ROM.cpp

couldn't find in vpath: BinaryROM.cpp

couldn't find in vpath: BinaryROMWriter.hpp

couldn't find in vpath: JVM.cpp

couldn't find in vpath: BytecodeOptimizer.cpp

couldn't find in vpath: ConstantPoolRewriter.cpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: MethodInvocationClosure.hpp

couldn't find in vpath: ROMTools.hpp

couldn't find in vpath: ROMProfile.hpp

couldn't find in vpath: ROMOptimizer.hpp

couldn't find in vpath: MethodInvocationClosure.cpp

couldn't find in vpath: ROMInliner.hpp

couldn't find in vpath: ROMInliner.cpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: ROMWriter.hpp

couldn't find in vpath: ROMProfile.cpp

couldn't find in vpath: SourceROMWriter.hpp

couldn't find in vpath: SegmentedSourceROMWriter.hpp

couldn't find in vpath: SegmentedSourceROMWriter.cpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMTools.hpp

couldn't find in vpath: ROMProfile.hpp

couldn't find in vpath: ROMOptimizer.hpp

couldn't find in vpath: ROMWriter.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: SourceROMWriter.hpp

couldn't find in vpath: BinaryROMWriter.hpp

couldn't find in vpath: SegmentedSourceROMWriter.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMTools.hpp

couldn't find in vpath: ROMProfile.hpp

couldn't find in vpath: ROMOptimizer.hpp

couldn't find in vpath: ROMWriter.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: SourceROMWriter.hpp

couldn't find in vpath: BinaryROMWriter.hpp

couldn't find in vpath: BytecodeOptimizer.hpp

couldn't find in vpath: ConstantPoolRewriter.hpp

couldn't find in vpath: ROMStructsWriter.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMTools.hpp

couldn't find in vpath: ROMProfile.hpp

couldn't find in vpath: ROMOptimizer.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: BytecodeOptimizer.hpp

couldn't find in vpath: ConstantPoolRewriter.hpp

couldn't find in vpath: MethodInvocationClosure.hpp

couldn't find in vpath: ROMInliner.hpp

couldn't find in vpath: ROMWriter.hpp

couldn't find in vpath: SourceROMWriter.hpp

couldn't find in vpath: SegmentedSourceROMWriter.hpp

couldn't find in vpath: BinaryROMWriter.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: MethodInvocationClosure.hpp

couldn't find in vpath: ROMTools.hpp

couldn't find in vpath: ROMProfile.hpp

couldn't find in vpath: ROMOptimizer.hpp

couldn't find in vpath: ROMInliner.hpp

couldn't find in vpath: JVM.hpp

couldn't find in vpath: ROMWriter.hpp

couldn't find in vpath: SourceROMWriter.hpp

couldn't find in vpath: SegmentedSourceROMWriter.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

couldn't find in vpath: ROMImage.hpp

couldn't find in vpath: OS.hpp

couldn't find in vpath: ROM.hpp

make[1]: Leaving directory `/home/phoneme_feature/build_output/cldc/
linux_arm_926/loopgen/app'

make[1]: Entering directory `/home/phoneme_feature/build_output/cldc/
linux_arm_926/loopgen/app'

==================================================

GNU_TOOLS_DIR = /usr/local/buildroot/build_arm/staging_dir

==================================================

mkdir -p ../bin

mkdir -p ../../dist/bin

mkdir -p ../../dist/lib

mkdir -p ../../dist/include

==============================

compiling cldc1.1 classes (98 files)...

preverifying classes...

make[2]: Entering directory `/home/phoneme_feature/build_output/cldc/
linux_arm_926/loopgen/app'

installed ../../dist/bin/preverify

make[2]: Leaving directory `/home/phoneme_feature/build_output/cldc/
linux_arm_926/loopgen/app'

rm -rf /home/phoneme_feature/build_output/cldc/classes.zip /home/
phoneme_feature/build_output/cldc/tmpclasses

==============================

generating ../generated/NativesTable.cpp ...

make[1]: *** No rule to make target `ROMImage.hpp', needed by
`FloatSupport_arm.o'. Stop.

make[1]: Leaving directory `/home/phoneme_feature/build_output/cldc/
linux_arm_926/loopgen/app'

make: *** [_loopgen] Error 2

[root@localhost phoneme_feature]#

danila
Offline
Joined: 2006-09-25
Points: 0

Hi gammy,

try to build for your host platform first, linux_i386 config.

Also, could you please send us the environment variable settings you used for the build?

Thanks,
Danila

gammy
Offline
Joined: 2008-01-08
Points: 0

Hi danila,

I have succesfully build CLDC for i386, and now i am trying for ARM9.

here is the detail of the shell script that i use to build.

setup.sh

export MEHOME=/home/phoneme_feature

mkdir $MEHOME/build_output

export BUILD_OUTPUT_DIR=$MEHOME/build_output

export JDK_DIR=/usr/java/j2sdk1.4.2_16

export PATH=$JDK_DIR/bin:$PATH

export Log=$MEHOME/log.txt

pcsl.sh

echo -e "\033[36m Starting PCSL build"

. setup.sh

export PCSL_OUTPUT_DIR=$BUILD_OUTPUT_DIR/pcsl

export PCSL_PLATFORM=linux_i386_gcc

cd $MEHOME/pcsl

# NETWORK_MODULE=bsd/qte \
make \
NETWORK_MODULE=bsd/generic \
$1

export PCSL_PLATFORM=linux_arm_gcc

export GNU_TOOLS_DIR=/usr/local/buildroot/build_arm/staging_dir

# NETWORK_MODULE=bsd/qte \
make \
NETWORK_MODULE=bsd/generic \
$1

if [ $? -ne 0 ]; then

echo "build-pcsl=failed" >> $Log

else

echo "build-pcsl=OK" >> $Log

fi

echo -e "\033[30m *****************************************************"

cldc.sh

echo -e "\033[31m Start of CLDC build"

. setup.sh

export JVMWorkSpace=$MEHOME/cldc

export JVMBuildSpace=$BUILD_OUTPUT_DIR/cldc

export GNU_TOOLS_DIR=/usr/local/buildroot/build_arm/staging_dir

cd $MEHOME/cldc/build/linux_arm_926

make \
GNU_TOOLS_DIR=$GNU_TOOLS_DIR \
ENABLE_PCSL=true \
PCSL_OUTPUT_DIR=$BUILD_OUTPUT_DIR/pcsl \
ENABLE_ISOLATES=true \
#GNU_TOOLS_DIR=/usr/local/buildroot/build_arm/staging_dir \

$1

if [ $? -ne 0 ]; then

echo "cldc_status=failed" >> $Log

else

echo "cldc_status=OK" >> $Log

fi

echo -e "\033[30m *************************************"

danila
Offline
Joined: 2006-09-25
Points: 0

Hi gammy,

the build fails, as the makedep utility fails to process the include database file properly.
Could you rerun the CLDC build with VERBOSE_BUILD=true,
so that we can check the command-line arguments for makedep?

Thanks,
Danila

gammy
Offline
Joined: 2008-01-08
Points: 0

Hi paolopaolo,

i am gammy, i read that you have successfully build the PhoneMe feature on i386,ARM. i have also Build on i386 and i am trying to build on ARM but i dont know how to use toolchain and how to give its path for the cross compilation for ARM. Please help me in solving this problem.

Thanks in Advance

omone
Offline
Joined: 2007-07-25
Points: 0

Hi gammy,
you have to export GNU_TOOLS_DIR variable pointing to the directory where you have your toolchain installed

gammy
Offline
Joined: 2008-01-08
Points: 0

Hi omone

Actuall first i want to cross compile Qtopia for ARM or qt and then i want to cross compile PhoneMe for ARM so please help me.I am giving the method followed by me i think i am giving the path of tool chain wrong so if u know how to cross compile Qtopia for the ARM please help me.

staging_dir=Tool_Chain.
i have kept the Qtopia in tmp folder i think it will not matter.
please tell me if i am assigning the path to variables correctly.

please help me!!!!!!!!!!!!!

[root@localhost qtopia-free-2.2.0]# export path=/root/staging_dir/arm-linux/bin
[root@localhost qtopia-free-2.2.0]# export QTDIR=/tmp/qtopia-free-2.2.0/qt2/bin
[root@localhost qtopia-free-2.2.0]# export TMAKEDIR=/tmp/qtopia-free-2.2.0/tmake
[root@localhost qtopia-free-2.2.0]# export TMAKEPATH=$TMAKEDIR/lib/linux-g++
[root@localhost qtopia-free-2.2.0]# export PATH=$QTDIR/bin:$PATH
[root@localhost qtopia-free-2.2.0]# export LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH
[root@localhost qtopia-free-2.2.0]# make qte
/tmp/qtopia-free-2.2.0/qtopia/scripts/buildQtopia -build qte
Qtopia Tools exist.

***********************************
********* Build Qt/Embedded *******
***********************************
QTE_CFG="-embedded -no-xft -qconfig qpe -qvfb -depths 4,8,16,32 -system-jpeg -gif -D QT_TRANSFORM_VFB -release -platform 'linux-g++' -xplatform 'linux-generic-g++'"

This is the Qt/Embedded Free Edition.

You are licensed to use this software under the terms of
the GNU General Public License (GPL).

Type 'G' to view the GNU General Public License.
Type 'yes' to accept this license offer.
Type 'no' to decline this license offer.

Do you accept the terms of the license?
symlink created for src/tools/qconfig-qpe.h

This target is using the GNU C++ compiler (linux-g++).

Recent versions of this compiler automatically include
code for exceptions, which increase both the size of
the Qt library and the amount of memory taken by your
applications.

You may elect to re-run ./configure with the -no-g++-exceptions
option to compile Qt without exceptions. This is
completely binary compatible, and existing
applications will continue to work (like KDE 2).

Building on: linux-g++-shared
Building for: linux-generic-g++-shared

Thread support..................... no
Configuration...................... qconfig-qpe.h

Creating makefiles...
Qt is now configured for building. Just run make.
To reconfigure, run make clean and configure.

make[1]: Entering directory `/tmp/qtopia-free-2.2.0/qt2/src'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/tmp/qtopia-free-2.2.0/qt2/src'
[root@localhost qtopia-free-2.2.0]#

omone
Offline
Joined: 2007-07-25
Points: 0

Sorry gammy,
but I used a different approach to build qte because of the environment on wich I'm running Phoneme (openmoko has it's own tools), so I can't help you in you particular problem.
I suggest you to make all your questions in a new topic beacuse are not really inherent with paolopaolo (and mine) problem...

paolopaolo
Offline
Joined: 2008-01-03
Points: 0

Hi,

I saw in a previous post that:
---------------------------------------------------------------------------------------------------------
Basically, the VM build has the following major phases:
1.Build the interpreter loop generator (aka loopgen)
2.Build the ROM image generator (aka romizer, romgen)
3.Execute loopgen to generate interpreter loop
4.Execute romgen to generate ROM image
5.Build the target VM linking it with interpreter loop and ROM image.

loopgen and romgen are special flavors of the VM itself and they are build for the host platform. Thus, they should be built with host native toolchain. Target VM binary should be built with the target-specific toolchain.
------------------------------------------------------------------------------------------------------------------------

Hence, the VM is first compiled for the host platform, and this explains why when we compiled the cldc linking the library libOurLib.so compiled for arm, we got the following error:
--------------------------------------------------------------------------------------------------------------------------------
linking ASM loop generator: ../../loopgen/app/loopgen
/usr/bin/ld: skipping incompatible /home/user/libOurLib.so when searching for -lOurLib
(where /home/user/ is $OUR_LIB)
--------------------------------------------------------------------------------------------------------------------------------

However, we are still not able to invoke a function of the dynamic library (libOurlib.so) from a cldc cpp source file.

thanks,
paolo.

danila
Offline
Joined: 2006-09-25
Points: 0

Hi paolo,

it can be useful to set additional env variable VERBOSE_BUILD=true.
It will make the build more verbose and can help you to track build issues.

For the problem with additional library, you can try to link it only with the target VM build and not link it with loopgen or romgen.

In makefiles you can use make env IsTarget, which is set to true only when the target VM is built, like this:

ifeq ($(IsTarget), true)
....

In the source code, you can use CROSS_GENERATOR which is set to 1 in loopgen and romgen and set to 0 in the target VM.

omone
Offline
Joined: 2007-07-25
Points: 0

Hi danila,
we followed your suggestion and everything works well, thanks a lot!!

Now we have another problem. We need to add a native function to the CLDC because we want to call it from a Java source. Hence we added a c++ file in the directory cldc/src/vm/share/natives. This file includes invocations to KNI functions.
However when we compile it, the compiler returns this error:
-------------------------------------------------
/home/user/phoneme_feature/cldc/src/vm/share/natives/OURFILE.cpp:242: error: expected declaration before ‘}’ token
-------------------------------------------------

It seems that a bracket is missing, we checked the sources but it's all ok.
In our cpp file we include the "kni.h" header and we use the functions KNI_StartHandless, KNI_DeclareHandle, .... and so on. We saw that all the other cpp files in the same directory use KNI without problems. Should we add some particular header file?

Thanks again

danila
Offline
Joined: 2006-09-25
Points: 0

Hi omone,

please check that KNI_StartHandles() and corresponding KNI_EndHandles() are always
in the same scope.
Most likely the compilation fails because they are in different scopes.

omone
Offline
Joined: 2007-07-25
Points: 0

It worked well!
KNI_EndHandles() was in another scope than KNI_StartHandles().

Thank you very much danila for your useful support, now everything works well and the PhoneME correctly calls our native library during its own execution.

omone
Offline
Joined: 2007-07-25
Points: 0

Hi danila,
we managed to add the invocation of a new Java Library (which invokes a native Library) also in JSR120 implementation, but we have stopped very early.

When we modified CLDC sources adding our own library we chosed to put it in directory [i]$MEHOME/cldc/src/javaapi/cldc1.1/[/i] and everithing went well: our package was compiled togheter with CLDC sources and, thanks to your suggestions, we were able also to call native library.

Now the problem is that wherever we decide to put our Java package, the compiler seems to ignore it. In fact we tried to put [i]mypackage/MyClass.java[/i] in the following directories:
[i]$MEHOME/jsr120/src/protocol/sms/classes
$MEHOME/jsr120/src/protocol/share/
$MEHOME/jsr120/src/tool/wmatool/classes/
$MEHOME/jsr120/src/core/common/classes/[/i]
then we tried also to put it in the following MIDP directories:
[i]$MEHOME/midp/src/core/javautil/reference/classes/
$MEHOME/midp/src/restricted_crypto/reference/classes/[/i]

The error is always the same:
"...
...compiling 544 .java files and 7 generated .java files
[i][path: line:][/i] package mypackage does not exist
..."

Where can I put mypackage directory to make it "visible"? Should I modify some options to include it in the compilation?

Thanks very much