Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Native Development

Reply
Regular Contributor
0x29a
Posts: 68
Registered: ‎03-13-2012
My Device: Playbook

Re: Differences between libraries ? and Code Organization for NDK

Yeah I am using the Make files build system, it says if I put a "Makefile" inside the folder or sub directory it should recurse through and make those items if I attach a "Makefile.dnm" it will prevent that folder from being recursed through and made. I have tried doing that and it appears not to work

From the QNX Source Tree guide it says that make starts by recursively going down the tree to the bottomost make file then that references the  topmost make file common.mk and initiates the building of targets.  

Please use plain text.
BlackBerry Development Advisor
elena_laskavaia
Posts: 417
Registered: ‎10-27-2010
My Device: PlayBook

Re: Differences between libraries ? and Code Organization for NDK

So the if you have directory x and a and b inside it and you want to put source files in dirs a and b, you need to add to recurse rule into the makefile which is in x folder, something like
LIST=SOURCES
See http://www.qnx.com/developers/docs/6.4.1/neutrino/prog/make_convent.html#MORALIST
Please use plain text.
Regular Contributor
0x29a
Posts: 68
Registered: ‎03-13-2012
My Device: Playbook

Re: Differences between libraries ? and Code Organization for NDK

I have put sources into a folder Hoop and put the Makefile.mk  and I get this

make all
make -j 1 -CHoop -fMakefile all
make[1]: Entering directory `C:/ndk-2.0.0-workspace/vvvvvvv/Hoop'
make[1]: `all' is up to date.
make[1]: Leaving directory `C:/ndk-2.0.0-workspace/vvvvvvv/Hoop'

it doesn't compile it to .o files it jsut enters the directory and skips make 

 

Please use plain text.
Regular Contributor
0x29a
Posts: 68
Registered: ‎03-13-2012
My Device: Playbook

Re: Differences between libraries ? and Code Organization for NDK

The Makefile.mk contains the usual recurse idom and LIST = CPU btw

Please use plain text.
Regular Contributor
0x29a
Posts: 68
Registered: ‎03-13-2012
My Device: Playbook

Re: Differences between libraries ? and Code Organization for NDK

This is all I needed to do 

EXTRA_SRCVPATH=$(PROJECT_ROOT)/sourcefoldername

put it in the common.mk 

Please use plain text.
Regular Contributor
0x29a
Posts: 68
Registered: ‎03-13-2012
My Device: Playbook

Re: Differences between libraries ? and Code Organization for NDK

As for the library differences,

 

Momentics should not build x86 for Playbook at all, but it does build that varient
So that explains why the gnu c++ libraries are added. They are strictly for x86 builds possibly for the simulator 

Where as the arm varient uses the qnx based Dinkware libraries

Please use plain text.