LeafLabs Garden

A place to share, learn, and grow...

1. 

   gruvin
   Member

   Hi

   I'm new to Maple and ARM in general, not new to C++, Makefiles, AVRs, etc.

   Right now, all I'm trying to do is to figure out how to create a build environment for a classic, multiple .cpp and .h file, C++ project.

   In the Unix Toolchain doc (http://leaflabs.com/docs/unix-toolchain.html#starting-your-own-projects), it states ...

   "At a minimum, your include path should contain the directories ~/libmaple/libmaple and ~/libmaple/wirish/"

   But this is clearly much less than, "a minimum". Why? Because it does nothing to tell of the myriad of compiler options and other things apparently needed to actually compile code for the Maple. That is to say, it's not as if you can simply ...

   arm-none-eabi-g++ -o myprog -Iwirish_include_dir -Lmaple.a main.cpp source1.cpp etc.cpp

   ... since that surely leaves out a great deal of otherwise required stuff. There's no board definition for starters, not to mention having no path from there to an .elf and then .bin file.

   (I do want to use wirish libraries etc, at least at this stage -- since that is the whole point, I thought?)

   I tried to modify the suite of files (like support/make/build-rules.mk) used to build the single main.cpp "sketch", so that it would also compile and later link multiple files. But I failed miserably. The build rules use some kind of compiler directive that seems to disallow multiple source files. Boohoo. I guess I'm not as clever with make (or g++) as I thought. :(

   So I'm really hoping someone can point me to an example of a, "large" project, which has a Makefile that can handle more than one source .cpp file.

   Much gratitude held in reserve for your generous kindness! :D

   Bryan.

   Posted 4 years ago #
2. 

   mbolivar
   LeafLabs

   Here's one:

   https://github.com/Ixox/preen

   I agree that the docs are weak there, though.

   Posted 4 years ago #
3. 

   gruvin
   Member

   Hmmm. After running a git pull, it seems I'm getting further with simply adding targets to build-targets.mk. My second file is now compiling and linking, I think.

   I'd still appreciate any advice or what I'm trying to achieve, as above. Thanks.

   Posted 4 years ago #
4. 

   robodude666
   Member

   I have been using a modified build-targets.mk file and found this strategy to work very well for me:

   https://gist.github.com/1181330

   Not only can I add new files very easily, I can change what my "main.cpp" file is without renaming them constantly to "main.cpp". I know it could be made better, with a foreach most likely but I'm too lazy to figure it out.

   Hopefully something like this can ship with a future release of libmaple. Not being very good at writing Makefiles, it was a bit annoying to figure this out initially. PreenFM was an inspiration to my modifications.

   Posted 4 years ago #
5. 

   gruvin
   Member

   Thanks for that. What you've done there is about where I'd got to last night, before a much needed sleep. Upon waking this morning, what needed to be done was suddenly more clear.

   The following is what I've ended up with, which is working a treat, though in my case there's only one build directory and all my .cpp source files are in the libmaple root dir, where main.cpp would normally be.

   The key parts for simplifying your file are the CXXSRC = and OBJECTS = parts. Note also the single build rule, using simply $(BUILD_PATH)/%o: %.cpp. There's no need for foreach, as such. It's kind of built right in.

   You could add a CCSRC and another build rule for handling .c files, if you have them.

   So here's the top (only part changed) section of my build-targets.mk ...

   CXXSRC = main.cpp gcode_process.cpp

   # Define all object files from list of C++ source files in CXXSRC
   OBJECTS = $(CXXSRC:%.cpp=$(BUILD_PATH)/%.o)

   $(BUILD_PATH)/%.o: %.cpp
   [tab]$(SILENT_CXX) $(CXX) $(CFLAGS) $(CXXFLAGS) $(LIBMAPLE_INCLUDES) $(WIRISH_INCLUDES) -o $@ -c $<

   $(BUILD_PATH)/libmaple.a: $(BUILDDIRS) $(TGT_BIN)
   [tab]- rm -f $@
   [tab]$(AR) crv $(BUILD_PATH)/libmaple.a $(TGT_BIN)

   library: $(BUILD_PATH)/libmaple.a

   .PHONY: library

   $(BUILD_PATH)/$(BOARD).elf: $(BUILDDIRS) $(TGT_BIN) $(OBJECTS)
   [tab]$(SILENT_LD) $(CXX) $(LDFLAGS) -o $@ $(TGT_BIN) $(OBJECTS) -Wl,-Map,$(BUILD_PATH)/$(BOARD).map

   Posted 4 years ago #
6. 

   gbulmer
   Moderator

   gruvin -Maybe you need to use a code tag or backtick quotes to preserve the spaces in that Makefile example?

   Edit: okay the [tab] works for me :-)

   Posted 4 years ago #
7. 

   gruvin
   Member

   Back-ticks just printed verbatim. I'll try code.

   Meanwhile, whilst my make now works as wanted, using the above, I note that it's not computing dependencies properly. If I edit one of the CXXSRC files, make isn't re-compiling it. (I have to do a make clean and recompile the whole project, which is a pain.)

   *shrug* What a mysterious, awkward program gmake is to understand. :/

   Posted 4 years ago #
8. 

   gruvin
   Member

   Oh. It won't let me edit the old post. Oh well. Here's a test, using code tags ...

   <br />
   first line<br />
           second line (spaces, not tab. *shrug*)<br />

   Nope. That doesn't work either. And see now when editing, It's replaced the code tags with back-ticks. Tidy forum this, but woefully under-featured. Oh well.

   LOL! After re-saving, once the back-ticks had replaced the code tags, now we're seeing the spaces! Oh and look, it added broken br tags too. Good grief. I give up.

   Grr. OK. No, I'll try one more time. This time with no blockquote and using back-ticks from the start ...

   first line
           second line (8 spaces prefixed)

   yay! Now inside a blockquote? ...

   first line
           second line (8 spaces prefixed)

   Dang. It worked. I didn't put the back-ticks on their own line in the early attempt. So there you go. It can be done. Oh for a simple preview-before-post function. (And it broke again when I edited. Had to fix it once more. Now I definitely give up. This thing is buggy as hell.)

   Posted 4 years ago #
9. 

   robodude666
   Member

   Easy as 123:

   opening backtick
   first line of code
   	hard tab
   close backtick

   Posted 4 years ago #
10. 

    gruvin
    Member

    Uhuh. Try that. Then edit the post and see how it gets messed up. *shrug* :D

    Posted 4 years ago #
11. 

    mbolivar
    LeafLabs

    line 1
    line2	hard tab
    line 3

    edit: some stuff

    edit 2: don't know what you tried, gruvin, but that works fine for me. it's probably best not to put code blocks in blockquotes; i imagine that's what's confusing the forum software.

    Posted 4 years ago #
12. 

    perry
    Administrator

    Hi Gruvin,

    It should be sufficient to make your own directory foo, then add it to
    LIBMAPLE_MODULES in the top-level Makefile.

    In foo, copy the rules.mk file out of say, wirish/ or libmaple/ and substitute
    the source files with your source files. That will compile everything with
    the standard build flags.

    -perry

    Posted 4 years ago #
13. 

    gruvin
    Member

    Thanks Perry. I'm having a play with that now. Looks promising.

    Question: How do these rules.mk files work in terms of multiple BUILDDIRS? I mean, how does the compiler/linker know which files to put in which BUILDDIR? I can't see anywhere how this is managed. :/

    Example from wirish/rules.mk ...
    

    BUILDDIRS       += $(BUILD_PATH)/$(d)
    BUILDDIRS       += $(BUILD_PATH)/$(d)/comm
    BUILDDIRS       += $(BUILD_PATH)/$(d)/boards

    Thanks again.

    Posted 4 years ago #
14. 

    gruvin
    Member

    Oh ... (I always seem to 'get it' just after posting on the forum! :-/) ... maybe it's as simple as following the same path prefixes in sppSRCS_$(d) ? Example ...

    cppSRCS_$(d) := wirish_math.cpp      \
                    Print.cpp                \
                    boards.cpp               \
                    boards/maple.cpp         \
                    boards/maple_mini.cpp    \
                    boards/maple_native.cpp  \
                    boards/maple_RET6.cpp    \
                    comm/HardwareSerial.cpp  \
                    comm/HardwareSPI.cpp     \
                    HardwareTimer.cpp        ...

    So then, I guess I just just don't have to specify a new BUILDDIR for my "directory foo". I'll try it and see.

    Posted 4 years ago #
15. 

    gruvin
    Member

    Hmm. It doesn't seem to work. The includes path doesn't seem to get carried into my module dir, like it probably should ...

    [CXX]       ./pnp/dda.cpp
    In file included from ./wirish/wirish.h:39,
                     from pnp/dda.cpp:31:
    ./wirish/boards.h:129: fatal error: maple_mini.h: No such file or directory
    compilation terminated.
    make: *** [build/./pnp/dda.o] Error 1

    The file maple_mini is in /wirish/boards/. There was no trouble finding it from within this same nest level when my files were all in the libmaple root.

    I'm once again out of my depth trying to debug and fix this. (It's also part of the libmaple code base, which I don't want to modify.) These are very complex Makefiles etc, by my usual standards.

    Posted 4 years ago #

RSS feed for this topic

Reply »

You must log in to post.