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


Thank you for visiting the BlackBerry Support Community Forums.

BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)

BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.

"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."

- Kevin Michaluk, Founder, CrackBerry.com

Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.


Reply
Highlighted
Regular Contributor
Posts: 68
Registered: ‎03-13-2012
My Device: Playbook
My Carrier: Rodgers

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.  

BlackBerry Development Advisor
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
Regular Contributor
Posts: 68
Registered: ‎03-13-2012
My Device: Playbook
My Carrier: Rodgers

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 

 

Regular Contributor
Posts: 68
Registered: ‎03-13-2012
My Device: Playbook
My Carrier: Rodgers

Re: Differences between libraries ? and Code Organization for NDK

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

Regular Contributor
Posts: 68
Registered: ‎03-13-2012
My Device: Playbook
My Carrier: Rodgers

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 

Regular Contributor
Posts: 68
Registered: ‎03-13-2012
My Device: Playbook
My Carrier: Rodgers

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