Perhaps you guys should get round to trying to build the examples on Linux. :-)
One difference between the two OS's is case sensitivity...
LPC17XX != LPC17xx
Perhaps you guys should get round to trying to build the examples on Linux. :-)
One difference between the two OS's is case sensitivity...
LPC17XX != LPC17xx
lpc17xx.h != LPC17xx.h
Yes we will eventually get around to this. However, if you get to it first we would appreciate a copy of your efforts and will happily fold them into the next release.
Thanks for your comments!
lpcUSBLib != lcpUSBlib
hey, why don't you create a new issue on the bug tracker regarding this
There is a new release up that you can try out where we addressed your issues relating to Linux builds. Please give it a try and let us know how it goes.
Right, just downloaded 0.91 Beta and all is good. Everything runs through fine. Two further points/questions though:
(i) in your 'built it' guide you should put the menu path on how to get to the Indexer settings. I had to google it. For anyone else wondering, Window ->Preferences ->C/C++ ->Indexer
(ii) regarding compilation, why does every configuration get built? I assumed that setting the active build would mean only that config would get built.
Thanks a lot.
Thanks for your feedback. We are happy that you are able to now build in Linux.
In response to your two comments:
1. We updated the "Configure the Projects" section of the Build It page to include the path to the indexer. Thanks for the heads up.
2. There are two aspects with the compilation process that might answer your question. First, the source files for the different configurations are wrapped entirely in #ifdefs for their particular configuration. So even though they all get built, most of them are just empty C files and so should compile very quickly. This is done as an interim step along the way towards our goal of having a merged driver library. The next step for us is to extract all the common code (more than 70%) into a single set of files and merge the remaining chip specific code into another set of files.
The other aspect is the tool, which I have noticed will just recompile everything for no good reason that I can determine. We will be working with Code Red on this in the near future.
I agree with point (i) I had the same experience.
Marco