Greetings Vasile, One of the stated purposes of Sourceforge, and probably GoogleCode too, is to never delete the old source code.
Actually, I do save the compiler source, binaries, and libraries, so I can't imagine the situation you are describing. Unless, I misplace that CD I burned. :-) Back to the topic - I don't want to see extra code generated for every library -- that seems wasteful of code space. Willliam On Oct 10, 4:50 am, vasile surducan <[email protected]> wrote: > William, > > imagine you want to compile and get a hex file for a project written 5 years > ago. > You dind't saved the compiler itself (good job picshell) and you have 20 > different files for the project and 2-3 different files for the libraries. > How do you manage such problem? > > Vasile > > On 10/9/09, William <[email protected]> wrote: > > > > > > > Perhaps I'm missing something, but why not generate a new include/ > > library (for example 'packrev.jal' ) "on the fly" and place it into > > the 'pack' ? This file would just have the revision of SVN (at the > > trunk) that was used to create the entire 'pack' . > > > And you could add an 'include packrev.jal' from some central place, > > say in the device files, like chipdef_jallib is handled. > > > William > > > On Oct 9, 10:36 am, Sebastien Lelong <[email protected]> > > wrote: > > > Let's continue this discussion on jallib. > > > > Seb > > > > > Maybe a stupid question, but is it possible to time stamp or place a > > > > version in every library at the moment they are placed in the release > > > > package ?. > > > > Now it is not easy to check whether you have the latest version or > > > > not. > > > > > This is a very valid question. Stef had some feature to report the > > version > > > > number of a library (and an ID as well), but the version number was > > > maintained manually (with the risk of different version with the same > > > number). Furthermore, I don't know how the version was actually used. > > > What would be usefull is that the SVN or weekly_build version of each > > > library becomes part of the asm file. This would enable us to go back > > > (close) to an orginal build situation. > > > I don't know how to achieve this though. Maybe we could put one ASM NOP > > line > > > in each library and put the version number and filename + path as comment > > > behind it. This does not take too much flash memory and it could be > > optional > > > (default on!) for the one's that need the last byte of flash. Would this > > > work? And what would it take to automagicly add such a line in each > > libary > > > file? > > > > BTW I don't know if it this is ontopic in jaluino, but it sure is on > > > jallib... I'm not too happy about Yet Another List for each topic... > > > > 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 -~----------~----~----~----~------~----~------~--~---
