search

hut2012 / imsdroid

Automatically exported from code.google.com/p/imsdroid
0 stars 0 forks source link

tiny* makefile incorrect behaviour #49

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I have found a mistake in your android-projects/makefile. The case is, you are 
using (cd ../$(PROJECT) ; $(MAKE) -f droid-makefile all; cp --force 
lib$(PROJECT).$(EXT) $(OUTPUT_DIR)) combo there, and if any project's make 
fails that does not mean the whole libtinyWRAP.so build process is going to 
fail since you get the result of the cp command as the last command result. 
During my experiments, I have made a mistake in the c code of tinyDAV project, 
but the buildAll.sh script kept working and producing the tinyWRAP library with 
the old version of tinyDAV, and since during compilation process there are 
loads of text going through the terminal, I haven't noticed a thing and kept 
experimenting... with no result at all. Only after some serious time I've 
realised the fact, that tinyDAV isn't being compiled at all! Attached is the 
patch to makefile fixing the issue, check it out please, it is a very serious 
problem!

Original issue reported on code.google.com by volkov.r...@gmail.com on 2 Sep 2010 at 8:51

Attachments:

GoogleCodeExporter commented 9 years ago 
there is another potential error - please check it out. If I enter the 
android-projects folder, and, say, accidentally do the make PROJECT=tinyDAV all 
command in order to rebuild the tinyDAV library (notice I forgot the BT=static 
switch), then the module appears as libtinyDAV.so in the output folder. Now, if 
I call the buildAll script it builds all the libtiny*.a libraries, but it seems 
as due to current script configuration, my .so library will be included in the 
tinyWRAP release instead of the .a one. And any try to use the libtinyWRAP.so 
solely will cause the UnsatisfiedLinkError. I cannot be 100% sure on that one, 
it needs confirmation from others, but it seems like what I've seen today until 
I wiped out the whole output directory. Maybe this needs to be done 
automatically.

Original comment by volkov.r...@gmail.com on 2 Sep 2010 at 11:19

GoogleCodeExporter commented 9 years ago

Original comment by boss...@yahoo.fr on 2 Sep 2010 at 7:41

GoogleCodeExporter commented 9 years ago

Original comment by boss...@yahoo.fr on 5 Oct 2010 at 5:00