LeafLabs Garden

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

1. 

   jonatan.olofsson
   Member

   Hi,

   I prefer to work from the commandline with the makefiles, compilers and the IDE of my choice. However, I have found it difficult to setup a directory structure that work well that will both work and not having to rebuild the entire libmaple all the time.
   The structure i'm looking for is something as follows:

   - libmaple
   - my_library
   - my_project
   - - Makefile with upload etc.

   Is there any way you recommend setting this up? Again, currently it refuses to acknowledge libmaple as already built on each build, but i'm only using the default makefile with minor modifications to include the library i'm writing. The more heavily modded makefile i tried to make failed to map the memory correctly for some reason..

   It would be very helpful for a setup with multiple maple projects!

   Posted 3 years ago #
2. 

   feurig
   Member

   Jonatan,
   I have been using a modified version of mbolivar's example project https://github.com/mbolivar/example-libmaple-project and using a directory structure like this.

   /libmaple
   /software/project
   /software/project/libraries

   This way i am able to update libmaple independently from my projects and all of my projects dependencies outside of libmaple are self contained and are stable.
   (With the exception of libmaple I don't like my libraries changing without me)

   hth: Don.

   Posted 3 years ago #
3. 

   lostinspacebar
   Member

   I keep my /libmaple directory in a "shared" or "common" folder where I keep other libraries, outside my projects folder.

   Something like

   ~/Shared/libmaple
   ~/Projects/myProject

   Posted 3 years ago #
4. 

   dipspb
   Member

   Pull req sent to https://github.com/mbolivar/example-libmaple-project/pull/1
   Helper script has been converted to Makefile to use it in a more natural way with Eclipse CDT.

   regards,
   Dmitry

   Posted 3 years ago #

RSS feed for this topic

Reply

You must log in to post.