Re: [lwip-users] multiple timers.c in project
At 19:14 18.07.2014, FreeRTOS Info wrote: On 18/07/2014 17:32, Simon Goldschmidt wrote: Sebastian Subik wrote: I hoped that there are better solutions available, but your solution should definitely work. Maybe lwip can consider renaming their timers.c within a future release to avoid such kind of problems... You could ask the same from FreeRTOS. In fact, sarcasm why doesn't every project rename every source file to have the project name as a prefix? That would be a great idea! /sarcasm There are a couple of things it would be nice to have the freedom to change in FreeRTOS - the file names is top of the list. List.c in particular - would be better as FreeRTOS_List.c. I really don't think it is any hassle to change the name of one file in your project though - but do understand it is more problematic when it comes to header file name clashes. When FreeRTOS was created, and probably lwIP too, there was no anticipation of its massive uptake, hence it maybe lacked a bit of forward thinking about how it would fit into larger projects. On top of that, at the time it was created, the file names all had to fit into 8.3 format too. Nearly all such if only we had done... wishes have been morphed into FreeRTOS over the years, and our newer products (both written already and being written) do not have these naming problems. We can't, however, change the name of a file for such a well established product as the core FreeRTOS kernel though without causing a major upset - there are so many third party tools that use the files, or copy the files around, or display the files, etc. and that is not even mentioning the thousands and thousands of users who would have to change their project files and scripts in order to update their version of FreeRTOS were the file names to change (a process that normally just requires a drop in replacement followed by a clean build). Just an idea, I'm not concerned by this problem (yet): What about renaming the files to some project_content.ext scheme, then creating files in the old content.ext scheme that just #includes the project_content.ext files? New user projects or those with the mentioned problems can use the new scheme, existing projects can use the old scheme and don't need to be adjusted. bye Fabi ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
Re: [lwip-users] multiple timers.c in project
Fabian Cenedese wrote: Just an idea, I'm not concerned by this problem (yet): What about renaming the files to some project_content.ext scheme, then creating files in the old content.ext scheme that just #includes the project_content.ext files? New user projects or those with the mentioned problems can use the new scheme, existing projects can use the old scheme and don't need to be adjusted. New users will most definitely include both C files into their project and be confronted with numerous duplicate symbol errors. I just don't get why there are still compiler environments that cannot handle multiple files with same filenames. I recently heard someone invented directories to solve issues like this... :-) Simon ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
Re: [lwip-users] multiple timers.c in project
On 22 July 2014, quoth Simon Goldschmidt: I just don't get why there are still compiler environments that cannot handle multiple files with same filenames. I recently heard someone invented directories to solve issues like this... :-) There are two different (but related) things that could lead to object collision: 1. Having the object files output to the same folder. This is readily solved by simply changing the output folders. 2. Having the object files linked into the same static library. This occurs because the object filename is stored without path in the static library format. The only real solution to it is to put the files into separate static libraries, which can occasionally be inconvenient, particularly when that would create circular references. There are usually ways to work around that, however. It shouldn't bother the linker at all to get files with the same name from explicit arguments and one or more static libraries; this is fairly common in fact. So provided that lwIP and FreeRTOS or whatever else might be conflicting with them are linked into separate static libraries (typically separate projects) then the problems should go away. (I recognise that my use of the verb link might be confusing above, as static libraries are created without the aid of a linker. But most of the alternatives sounded worse.) ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
Re: [lwip-users] multiple timers.c in project
Maybe I should move this thread to the CrossStudio mailing list... I am sure, they are able to deal with this, but I don't know how to configure the IDE... :=) Sebastian Am 22.07.2014 um 09:08 schrieb Simon Goldschmidt goldsi...@gmx.de: . I just don't get why there are still compiler environments that cannot handle multiple files with same filenames. I recently heard someone invented directories to solve issues like this... :-) Simon ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
Re: [lwip-users] multiple timers.c in project
Sebastian Subik wrote: I am using lwip on freeRTOS 7.4.2 and everything is working. Now I would like to use additionally the freeROTS timer (defined in timers.c). The problem is that my CrossStudio has some linking problems, I think it could not deal with two timers.c within the same project. Although this is not a lwip problem, maybe anyone has faced the same? ST has obviously 'solved' this by renaming 'timers.c' to 'lwip_timers.c', but I'd rather suggest to fix your build to not put all '.o' files in one single directory, which should fix it, too. Although I heard some IDEs make it really hard to do so... Simon ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
Re: [lwip-users] multiple timers.c in project
Thanks Simon, I hoped that there are better solutions available, but your solution should definitely work. Maybe lwip can consider renaming their timers.c within a future release to avoid such kind of problems... Best Sebastian -Ursprüngliche Nachricht- Von: lwip-users-bounces+ss=piciorgros@nongnu.org [mailto:lwip-users-bounces+ss=piciorgros@nongnu.org] Im Auftrag von Simon Goldschmidt Gesendet: Freitag, 18. Juli 2014 11:02 An: Mailing list for lwIP users Betreff: Re: [lwip-users] multiple timers.c in project Sebastian Subik wrote: I am using lwip on freeRTOS 7.4.2 and everything is working. Now I would like to use additionally the freeROTS timer (defined in timers.c). The problem is that my CrossStudio has some linking problems, I think it could not deal with two timers.c within the same project. Although this is not a lwip problem, maybe anyone has faced the same? ST has obviously 'solved' this by renaming 'timers.c' to 'lwip_timers.c', but I'd rather suggest to fix your build to not put all '.o' files in one single directory, which should fix it, too. Although I heard some IDEs make it really hard to do so... Simon ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
Re: [lwip-users] multiple timers.c in project
Sebastian Subik wrote: I hoped that there are better solutions available, but your solution should definitely work. Maybe lwip can consider renaming their timers.c within a future release to avoid such kind of problems... You could ask the same from FreeRTOS. In fact, sarcasm why doesn't every project rename every source file to have the project name as a prefix? That would be a great idea! /sarcasm :-) Simon ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
Re: [lwip-users] multiple timers.c in project
Hi, On Fri, Jul 18, 2014 at 06:32:57PM +0200, Simon Goldschmidt wrote: Sebastian Subik wrote: I hoped that there are better solutions available, but your solution should definitely work. Maybe lwip can consider renaming their timers.c within a future release to avoid such kind of problems... You could ask the same from FreeRTOS. In fact, sarcasm why doesn't every project rename every source file to have the project name as a prefix? That would be a great idea! /sarcasm I discovered recently that we created filesystems with a directory tree which should solve in a elegant way the problem mentioned before, I couldn't believe it ! Oh... wait... ;-) Sylvain signature.asc Description: Digital signature ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
Re: [lwip-users] multiple timers.c in project
On 18/07/2014 17:32, Simon Goldschmidt wrote: Sebastian Subik wrote: I hoped that there are better solutions available, but your solution should definitely work. Maybe lwip can consider renaming their timers.c within a future release to avoid such kind of problems... You could ask the same from FreeRTOS. In fact, sarcasm why doesn't every project rename every source file to have the project name as a prefix? That would be a great idea! /sarcasm :-) Simon There are a couple of things it would be nice to have the freedom to change in FreeRTOS - the file names is top of the list. List.c in particular - would be better as FreeRTOS_List.c. I really don't think it is any hassle to change the name of one file in your project though - but do understand it is more problematic when it comes to header file name clashes. When FreeRTOS was created, and probably lwIP too, there was no anticipation of its massive uptake, hence it maybe lacked a bit of forward thinking about how it would fit into larger projects. On top of that, at the time it was created, the file names all had to fit into 8.3 format too. Nearly all such if only we had done... wishes have been morphed into FreeRTOS over the years, and our newer products (both written already and being written) do not have these naming problems. We can't, however, change the name of a file for such a well established product as the core FreeRTOS kernel though without causing a major upset - there are so many third party tools that use the files, or copy the files around, or display the files, etc. and that is not even mentioning the thousands and thousands of users who would have to change their project files and scripts in order to update their version of FreeRTOS were the file names to change (a process that normally just requires a drop in replacement followed by a clean build). Regards, Richard. + http://www.FreeRTOS.org Designed for microcontrollers. More than 107000 downloads in 2013. + http://www.FreeRTOS.org/plus IoT, Trace, Certification, FAT FS, TCP/IP, Training, and more... ___ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
