Timeline for Different ways to distribute (embedded) C modular library
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 24, 2017 at 14:57 | audit | Close votes | |||
| Jan 24, 2017 at 14:57 | |||||
| Jan 1, 2017 at 20:11 | vote | accept | Phalox | ||
| Jan 1, 2017 at 12:00 | comment | added | Doc Brown | @Phalox: cmake itself is cross-platform, it is an established standard for a huge number of platforms, and it can generate project/makefiles for almost any sensible build system the users of your lib might be using. Nevertheless you are right: it makes things probably more complicated than distributing a single .h/.c file without any platform specific project or makefiles. | |
| Jan 1, 2017 at 10:31 | comment | added | Phalox | Hi @DocBrown Correct me if I'm wrong, but if you're using picoTCP as a library, and want to incorporate it into an existing project, won't you make matters worse if you impose a specific build system on the user? | |
| Dec 31, 2016 at 9:09 | comment | added | Doc Brown | Can't you utilize cmake? This will allow to generate Makefiles or Visual Studio project files for all kind of different targets? | |
| Dec 31, 2016 at 8:51 | history | tweeted | twitter.com/StackSoftEng/status/815118085615132672 | ||
| Dec 31, 2016 at 8:50 | comment | added | Phalox | I've clarified this somewhat in the question. Our main concern is towards the end users who use picoTCP in their project. | |
| Dec 31, 2016 at 8:49 | history | edited | Phalox | CC BY-SA 3.0 | Clarified "development" |
| Dec 31, 2016 at 4:38 | answer | added | Blrfl | timeline score: 8 | |
| Dec 30, 2016 at 21:34 | comment | added | Jörg W Mittag | … developer, but I'm guessing you might get some interesting inputs from other developers as well, so maybe you could clarify that for those not deeply into the matter? Thanks! | |
| Dec 30, 2016 at 21:33 | comment | added | Jörg W Mittag | Not being an embedded and/or C developer, I am a little confused what you are asking about. It is unclear to me, when you say "development" do you mean development of a product using picoTCP or do you mean development of picoTCP? And when you say "focus on GCC", are you similarly referring to using GNU make/GCC to generate the distribution files from the development files or are you talking about building the final product that uses picoTCP? In your README, you mention a long list of supported compilers, so I guess it is the former? Maybe those points are obvious to an embedded … | |
| Dec 30, 2016 at 20:37 | history | edited | Phalox | CC BY-SA 3.0 | added 35 characters in body |
| Dec 30, 2016 at 20:32 | review | First posts | |||
| Jan 2, 2017 at 9:07 | |||||
| Dec 30, 2016 at 20:29 | history | asked | Phalox | CC BY-SA 3.0 |