<html><body><div><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body >Peter's statement gets a +1 for me. Makefile integration IMHO makes using RTEMS in many development systems rather easy. Forcing Waf for user development is a drawback. <div><br></div><div>How can we avoid this?</div><div><br></div><div>Wkr Thomas. </div><br><br><br>-------- Ursprüngliche Nachricht --------<br>Von: Peter Dufault <dufault@hda.com> <br>Datum: <br>An: Gedare Bloom <gedare@rtems.org> <br>Cc: Amar Takhar <verm@darkbeer.org>,"rtems-devel@rtems.org" <devel@rtems.org> <br>Betreff: Re: How will user's compile with Makefiles? Was: Re: large bss size for sample applications <br> <br><br></div><br><div>I don’t like this requirement. I think it’s fine for development but want to be able to deliver a package that will integrate into a client’s Makefile based build system where they can make changes and re-build. In other words, I don’t mind if building a BSP or updating RTEMS requires waf, but want to be able to deploy and make minor changes without it.<br><br>Up to now I’ve been able to get the existing Makefile fragments to work at multiple sites with a little work.<br><br>> On Sep 26, 2015, at 09:04 , Gedare Bloom <gedare@rtems.org> wrote:<br>> <br>> The comment below, made in the users ml, caught me off guard. How will<br>> user's applications build when RTEMS is built with Waf?<br>> <br>> If there is a complex answer, then this conversation belongs here on<br>> the devel ml until we can sort it out.<br>> <br>> Gedare<br>> <br>> On Sat, Sep 26, 2015 at 2:36 AM, Chris Johns <chrisj@rtems.org> wrote:<br>>> On 25/09/2015 11:04 pm, Jeff Webb wrote:<br>>>> On 09/25/2015 07:59 AM, Gedare Bloom wrote:<br>>>>>> The next task for me will be to set up a simple out-of tree C or C++<br>>>>>> POSIX<br>>>>>> application.<br>>>>>> <br>>>>>> Thanks again for all the help!<br>>>>>> <br>>>>>> -Jeff<br>>>>>> <br>>>>> <br>>>>> Simple examples for out-of-tree builds exist in the examples-v2.git<br>>>>> repository with the "RTEMS Application Makefile" approach using custom<br>>>>> Makefiles, and with the "RTEMS Application Waf" approach using<br>>>>> wscripts and a git-submodule for waf support. The former is an older,<br>>>>> established way to build applications linking to an 'installed' RTEMS,<br>>>>> and the latter is a newer way to do it.<br>>>> <br>>>> Perfect! This is just what I need. Thanks for the pointer.<br>>>> <br>>> <br>>> The Makefile approach will not be supported with the waf build of RTEMS<br>>> when it lands.<br>>> <br>>> Chris<br>>> _______________________________________________<br>>> users mailing list<br>>> users@rtems.org<br>>> <a href="http://lists.rtems.org/mailman/listinfo/users">http://lists.rtems.org/mailman/listinfo/users</a><br>> _______________________________________________<br>> devel mailing list<br>> devel@rtems.org<br>> <a href="http://lists.rtems.org/mailman/listinfo/devel">http://lists.rtems.org/mailman/listinfo/devel</a><br><br>Peter<br>-----------------<br>Peter Dufault<br>HD Associates, Inc. Software and System Engineering<br><br>This email, like most email, is delivered unencrypted via internet email protocols subject to interception and tampering. Contact HDA to discuss methods we can use that ensure secure communication.<br><br>_______________________________________________<br>devel mailing list<br>devel@rtems.org<br><a href="http://lists.rtems.org/mailman/listinfo/devel">http://lists.rtems.org/mailman/listinfo/devel</a></div></body></html>