Pages: 1 [2]   Go Down
Author Topic: [arduino 1.5] "Not a valid library" importing Bitlash  (Read 4644 times)
0 Members and 1 Guest are viewing this topic.
0
Offline Offline
God Member
*****
Karma: 39
Posts: 986
Get Bitlash: http://bitlash.net
View Profile
 Bigger Bigger  Smaller Smaller  Reset Reset

I've pushed an update to Bitlash that compiles and links cleanly with the ARM processor selections using the current github ide-1.5.x branch of the IDE.  It has a 4k simulated EEPROM situated in ram for function storage, for now, so your functions aren't saved through power off.

I don't have a Due handy, so I can't test it, but I'd love to hear field reports.


-br

Logged

Offline Offline
God Member
*****
Karma: 21
Posts: 650
View Profile
WWW
 Bigger Bigger  Smaller Smaller  Reset Reset

Question for C: is there an official #define that distinguishes the Due/Arm build from the AVR builds?

He's already covered that in this thread:

http://arduino.cc/forum/index.php/topic,128520.0.html
Logged

WiFi shields/Yun too expensive? Embeddedcoolness.com is now selling the RFXduino nRF24L01+ <-> TCP/IP Linux gateway: Simpler, more affordable, and even more powerful wireless Internet connectivity for *all* your Arduino projects! (nRF24L01+ shield and dev board kits available too.)

Nice, France
Offline Offline
Full Member
***
Karma: 11
Posts: 234
View Profile
 Bigger Bigger  Smaller Smaller  Reset Reset

The new IDE 1.5 has 'fat' libraries support: libraries that contains code to run on more than one microcontroller architecture. The advantages of having a 'fat' library are clear:
- The IDE will automatically lists the available libraries based on the architecture of the currently selected board
- The same library can have multiple architecture inside => you don't have to install a different version of the same library for every architecture.

These are good changes.

We also tried to introduce an auto-detection mechanism that takes apart non-fat libraries from fat libraries.
This mechanism didn't worked as expected because we assumed that library writers would only use 'examples' and 'utility' folder. This is a clearly wrong assumption, and the patch i have just pushed on the repository fixes this problem.
Pleased to hear that the feedback has been taken int account.

To make my position clear, some sort of cleanup by documented standard directory names is a good thing. Consolidating 'Example' and 'example' and 'examples' and suchlike variants into a single, documented name is a good thing (so the IDE can display te eample,s, in a menu).

Likewise for other directories on which the IDE has to automatically act. I could see integrated documentaton browsing, for example, if tyhere were standard ways to add it (doxygen seems to be popular). Keeping documentation close to code, and encouraging documentation, are clearly good thins.

On the other hand there may be a need for all sorts of other data, the form of which may ary wildly depending on the purpose of the library and thhe supported hardware. Libraries should be free to add what they need, since the IDE does not need to know about it or do anything with it. Same for setup utilities, python and perl scripts to generate config files or to consume data produced by the library, etc. Although having documented standard values ('data' and 'utils' for example) would help consistency.

I'll invite you all to check if the patch will fix the issues you are having.

https://github.com/arduino/Arduino/tree/ide-1.5.x
Yay. Checking.
Logged

Pages: 1 [2]   Go Up
Jump to: