OK -- temporarily, I went ahead and fixed this by adding the boards/ and comm/ prefixes in the following files ...
wirish/wirish.h:
...
#include "comm/HardwareSPI.h"
#include "comm/HardwareSerial.h"
...wirish/boards.h:
...
#elif defined(BOARD_maple_mini)
#include "boards/maple_mini.h"
...Maybe they should be like this in the first place? Or maybe I'm missing something?
This is definitely much tidier, using a module dir, as suggested.
I created a module directory ~/libmaple/pnp and moved all my .cpp/h files in there.
Then I removed the int main(void) function from my previous main.cpp (now renamed openpnp.cpp) and created an openpnp.h to export the setup() and loop() functions. Obviously, I moved the while (1) ... loop from the old main() function into loop().
I then copied ~/libmaple/wirish/rules.mk into my pnp/ module directory, and edited the cppSRCS_$(d) := ... part to list my source .cpp files. I also removed the two extra BUILDDIRS, at the top of the file, leaving only the first one, for the current directory.
So my ~/libmaple/main.cpp now looks like this ...
#include "pnp/openpnp.h"
int main(void) {
setup();
// main loop
while (1)
{
loop();
}
return 0;
}With the exception that I had to edit ~/libmaple/wirish/wirish.h and ~/libmaple/wirish/boards.h (see previous post, above), it's all working quite nicely.
Bryan.
frpr
Member
Hello,
how do I simply include "my.c", "my.h" to "Makefile" in order to be compiled with my "main.cpp" file?
All files are in my (~/_arm32) directory. They are based on the "blinky.cpp" project example.
Here is description of my problem (http://forums.leaflabs.com/topic.php?id=1013).
I don't want write explicitly a makefile rule for each my*.c, my*.h file.
I understand that the rules can be generated automatically (compiler -MM flag). It should be already done in file "build-rules.mk"
Please any example or advice for a newbie like me.
airthimble
Member
Tonight I was wondering this very thing myself.
Here is a solution I came up with that appears to be working for the moment.
Let's say that I have all my .cpp/.h files in a folder called "testFolder"
move testFolder so that it is in this location: ~/libmaple/libraries/testFolder
copy ~/libmaple/libraries/Servo/rules.mk into ~/libmaple/libraries/testFolder
now open up this file ~/libmaple/libraries/testFolder/rules.mk
about 10 or so lines down in the file there is a line that says 'cppSRCS_$(d) = something'
modify this line so that it includes your .cpp files
Next open up this file: ~/libmaple/Makefile
Somewhere around line 100 there is the tag '# Experimental Libraries'
add this line: LIBMAPLE_MODULES += $(SRCROOT)/libraries/testFolder
I think that should do it, frpr, if you would like to give it a test run and see if it works for you that would be great.
Ok, my turn to fight this battle. I've read through all of the above and I'm lost. I'm no stranger to writing c programs under unix and simple make files, but the make files we're dealing with here are a bit beyond my level of understanding.
So here's what I want to do - I've got the whole libmaple tree installed and I have a separate directory tree for my projects, eg ~/maple/project_a. If I 'setenv LIB_MAPLE_HOME ~/libmaple' (tcsh shell) and type 'make' it seems to compile all of the libmaple stuff and main.cpp, but not any of my other cpp files. So how do I get it to compile my project?
Thanks.
billw
Member
What I have done to get compiles to go from anywhere:
1) Copy over the libmaple/Makefile and libmaple/build-targets.mk to your project directory.
2) The Makefile will still use the libmaple/build-targets.mk, so you need to edit your project
Makefile to make it include your local build-targets.mk. So, under Targets change:
# main target
include $(SRCROOT)/build-targets.mk
to
# main target
include build-targets.mk
3) Edit your local build-targets.mk to add your other .cpp files as gruvin described
above, that is:
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
...
and so on as described in that post.
Maybe you've missed step 2? That's what gave me a problem for a while
when I was getting this going.
After this works, any new project can reuse the Makefile and build-targes.mk
and only change the CXXSRC line in build-targets.mk
Ok, #1 and #2 are no problem, they're very straightforward. #3 is where I'm lost. You say:
3) Edit your local build-targets.mk to add your other .cpp files as gruvin described
above, that is: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
...
and so on as described in that post.
My local build-targets.mk doesn't contain any of those lines. So ... I'm left wondering if I'm supposed to add them and if so, where? On a whim, I stuck them at the beginning of build-targets.mk. Amazingly enough, it sorta works. Except that part way through, before it ever gets to my files, it now barfs with:
"make: *** No rule to make target build//home/tdc218/libmaple/wirish/wirish_math.o', needed bybuild/maple_RET6.elf'. Stop."
Obviously that path is not right. Taking out the added lines reverts it back to just compiling main.cpp. So what else am I missing? Maybe this is part of the "add your other .cpp files as gruvin described above", except I can't figure out which post you're referring to.
billw
Member
Here's a minimal setup using two .cpp files.
http://members.dslextreme.com/users/billw/test/maple-demo.tar.z
You should be able to drop the Makefile and build-targets.mk into
your directory and only have to substitute in your .cpp files by changing
the CXXSRC line in build-targets.mk
by using the Makefile and build-targets.mk all I did was change the top of build-targets.mk to:
SOURCES = main.cpp \
ads1282.cpp
$(BUILD_PATH)/main.o: $(SOURCES)
$(SILENT_CXX) $(CXX) $(CFLAGS) $(CXXFLAGS) $(LIBMAPLE_INCLUDES) $(WIRISH_INCLUDES) -o $@ -c $<
then you can list all your .cpp or .c files in the SOURCES variable.
- gaute
Here's a Makefile that accepts multiple files, check the array at the top of the file. This one also defines GIT_DESC which I use to keep track of which version I am running.
https://github.com/gauteh/libmaple
- gaute
Bump. Ok, getting back to this a year later. Had it all working back when so tonight I fired up the Linux box, cd to my project, did a make, and it built fine.
Figuring that in a year plus there had probably been some updates I followed the instructions here http://leaflabs.com/docs/unix-toolchain.html#getting-updates and now when I do a make I get:
blockquote
/home/tdc/libmaple/support/make/target-config.mk:23: /maple_mini.mk: No such file or directory
make: *** No rule to make target `/maple_mini.mk'. Stop.
blockquote
I've confirmed that maple_nini.mk exists at ~/libmaple/support/make/board-includes/ but obviously it's not finding it. How do I fix this please and thank you?
ps - I apologize if bumping a year old thread is a breach of netiquette in these parts. It seemed the most logical place and the guidelines are silent on this issue.
You must log in to post.
