Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 3
    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 … Commented Dec 30, 2016 at 21:33
  • 1
    … 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! Commented Dec 30, 2016 at 21:34
  • 1
    I've clarified this somewhat in the question. Our main concern is towards the end users who use picoTCP in their project. Commented Dec 31, 2016 at 8:50
  • 2
    Can't you utilize cmake? This will allow to generate Makefiles or Visual Studio project files for all kind of different targets? Commented Dec 31, 2016 at 9:09
  • 1
    @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. Commented Jan 1, 2017 at 12:00