What I do now when developing/testing is to 'expand' the full jallib tree as an include path for the compiler. My main file only contains 2 lines like:
include board_16f877a_dwarf include i2c_test_l0 This way, I can build any test from the most recent files without the burden of (error prone) copying of files back and forth. For this, it is nescesarry that the board and test files have unique names and is good if there is some naming convention. Maybe we should use a test_ prefix on the test files, like we do with the board files. So, we don't agree (yet) if your statement also applies to test files. I don't have an opinion on the naming convention of sample files, as long as they don't interfere with libs, board and test files. Joep --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
