Adding libraries to SEGGER (or anything else, really)

[msmithRT]

I'm definitely not the first person to ask about this, and I probably won't be the last.

Am I being exceptionally dense, or is the nordic SDK exploded across dozens of folders and subfolders? Is there a simple and scalable way to add entire modules to emStudio? Normally with a new library you'd simply add the header file directory and the binary or C-file directory. I'm adding a dozen library paths per project, and it's starting to drive me up the wall. Copying code from a different sample project is a nightmare of trying to fix broken paths, not to mention broken sdk_config dependencies five layers of macro definitions deep.

[Nguyen Hoan Hoang]

LoL!!! it gets worst with every updates not to mention over 3000 defines to browse through to enable compilation of the source code that you already explicitly put in the project.  All the things that I always tell the any intern to absolutely avoid doing, they did them all. 

[msmithRT]

The funny (and infuriating) thing is that I was trying to make a dead-simple debug link to another chip I'm having a problem with. After wasting a good chunk of yesterday trying to set up what should have been less than fifty lines of code, it occurred to me that I'd save time and money by just hacking up my device and wiring in a dumb little arduino instead to debug the problem.

But that does still leave us wondering what's up with the library organization. Given the weird "Add the macro so you can enable the macro to enable the initializer to enable the code in the library you explicitly added" architecture, does Nordic just expect everybody to import everything by default?

[Nguyen Hoan Hoang]

Well said man! I like your quote : 

"Add the macro so you can enable the macro to enable the initializer to enable the code in the library you explicitly added"

LoL!!!