http://forums.leaflabs.com/topic.php?id=180 A place to share, learn, and grow... en-US Fri, 22 Jan 2016 00:12:55 +0000 http://bbpress.org/?v=1.0.2 q http://forums.leaflabs.com/search.php http://forums.leaflabs.com/topic.php?id=180#post-4610 Sat, 14 May 2011 19:32:38 +0000 robodude666 4610@http://forums.leaflabs.com/ <p>Nothing specific.</p> <p>After a few hours of messing around, and referencing my AVR makefiles, I ended up with something similar though not as pretty. I'll update my makefile later when I reorganize my project. </p> http://forums.leaflabs.com/topic.php?id=180#post-4604 Sat, 14 May 2011 17:41:53 +0000 mbolivar 4604@http://forums.leaflabs.com/ <p>robodude666,</p> <p>Not sure what you mean by "pretty" -- what sort of thing would you like?</p> <p>If you don't like the idea of linking against libmaple.a, you may be able to modify Xavier's setup in his preen project to your purposes:</p> <p><a href="https://github.com/Ixox/preen" rel="nofollow">https://github.com/Ixox/preen</a> </p> http://forums.leaflabs.com/topic.php?id=180#post-4600 Sat, 14 May 2011 15:04:45 +0000 robodude666 4600@http://forums.leaflabs.com/ <p>Until a pretty way for supporting multiple source files is released, is it possible to have some documentation on how to "hack" the <code>build-targets.mk</code> file to support multiple source files? I have my main.cpp file, but I also have a few other c and cpp files I need compiled. I could of course copy everything into main.cpp, but then I'd have an unorganized mess. </p> http://forums.leaflabs.com/topic.php?id=180#post-4516 Fri, 06 May 2011 17:50:59 +0000 mbolivar 4516@http://forums.leaflabs.com/ <p>Tokenekie,</p> <p>Modifying build-targets.mk was a hack I proposed so that snigelen could get his job done. The right thing to do for multiple source files is to link against a precompiled libmaple archive. Instructions for building a libmaple.a are in the top-level README of libmaple's master branch (at the bottom, section "Instructions to create a library"). (This information will be folded into the official 0.0.10 docs).</p> <p>If you're asking for more information about libmaple's build structure, it is based on the recommendations made in the paper "Recursive Make Considered Harmful":</p> <p><a href="http://miller.emu.id.au/pmiller/books/rmch/" rel="nofollow">http://miller.emu.id.au/pmiller/books/rmch/</a> </p> http://forums.leaflabs.com/topic.php?id=180#post-4501 Thu, 05 May 2011 17:15:25 +0000 Tokenekie 4501@http://forums.leaflabs.com/ <p>Sorry, I'm new to makefiles and build-targets.mk makes no sense to me right now.</p> <p>Where can I learn to understand the "prerequisites" of build-targets.mk if I need to compile other source files within my project folder during make? </p> http://forums.leaflabs.com/topic.php?id=180#post-1200 Mon, 13 Sep 2010 15:17:58 +0000 mbolivar 1200@http://forums.leaflabs.com/ <p>Great, glad to hear it! Let us know if you run into any more problems. </p> http://forums.leaflabs.com/topic.php?id=180#post-1199 Mon, 13 Sep 2010 15:11:44 +0000 snigelen 1199@http://forums.leaflabs.com/ <p>Yeah, that seems to work. I've got a small test.h/test.c to compile and link with the main program.<br /> Thanks! </p> http://forums.leaflabs.com/topic.php?id=180#post-1194 Mon, 13 Sep 2010 14:23:55 +0000 mbolivar 1194@http://forums.leaflabs.com/ <p>I see what you mean. The make rule which targeted main.o was previously in a pretty hidden place; I've pushed a change to our libmaple github repository which exposes it:<br /> $ cd $LIB_MAPLE_HOME<br /> $ git pull</p> <p>You should see some noise about build-targets.mk, and the top-level directory will then contain a file by that name. That's where the rule to build main.o lives. Copy it over to your project directory as well (the same way you did with the Makefile). Hopefully, you can add to its prerequisites to get everything to build correctly for your project; if you're using emacs and make, hopefully you know what that means.</p> <p>I realize that this is not too user-friendly and apologize, but we're all pushing towards IDE 0.0.7 at the moment. We'll fix things up later so you'll only have to edit a list of your c/c++ sources and update this thread then. </p> http://forums.leaflabs.com/topic.php?id=180#post-1193 Mon, 13 Sep 2010 13:05:52 +0000 snigelen 1193@http://forums.leaflabs.com/ <p>Yes header files are included. But the .c-files aren't compiled, and if I can make them be compiled, the wirish and libmaple directories aren't in the include path. And if I manage to get the include path there, the compiled object files aren't linked with the final app...</p> <p>But do you mean that if I have foo.h and foo.c (or .cpp) in the same directory as main.cpp it's supposed to work without mentioning any of them in the Makefile? In my tests it was diskio.h, sd_spi_stm32.c, ff.h, ff.c (i.e. not always .h/.c-pairs) for a start, but no .c file is compiled.</p> <p>(btw. I'm not talking about the IDE, I prefer to use emacs and make) </p> http://forums.leaflabs.com/topic.php?id=180#post-1191 Mon, 13 Sep 2010 12:45:43 +0000 mbolivar 1191@http://forums.leaflabs.com/ <p>If you have more than one file, they have to be #include-d from main.cpp as appropriate, but that should just work. Have you tried that? </p> http://forums.leaflabs.com/topic.php?id=180#post-1176 Mon, 13 Sep 2010 02:27:29 +0000 snigelen 1176@http://forums.leaflabs.com/ <p>How do I add more source files to the Makefile when using the Unix-toolchain? I've tried a lot of different things but there's always something missing. </p>