Martine, Yup. That's what it sounds like. I have to wonder why, since CCS gives as options for toolchain the following: Cross GCC, Microsoft Visual C++, MinGW GCC, and TI Build Tools. You would think they would been in the path already. If I choose MinGW GCC, I don't have the option to use external makefiles. That seems a bit odd, too. Another issue I am trying to figure out is how to configure the workspace/project such that CCS doesn't polute RIOT directory. It asks where to find the external code and then places the '.cproject' file in that folder. This is way more of a pain-in-the-ass than it needs to be, but that seems to be the open source/gnu way. "Let's see how ridiculously entangled and obfuscated we can make this"...
On Fri, Jun 24, 2016 at 1:13 PM, Martine Lenders <[email protected]> wrote: > Hey Clark, > that sounds something like the path to your make installation isn't > set in the environment variable PATH. I know from the past, that you > can set them somewhere in the system config, but I haven't used > Windows in years and when I did I had it in German, so don't ask me > were exactly (in WinXP you did it like this [1], just add the path to > make to the semicolon-seperated list of the variable PATH [or create > it, if it doesn't exist]). But maybe this hint is enough to give you > some context for a web search to get some more current information. > > Cheers, > Martine > > [1] https://support.microsoft.com/en-us/kb/310519 > > 2016-06-24 17:50 GMT+02:00 Clark Leach <[email protected]>: > > Hello Malo, > > I gather that you are building this as a CCS project rather than an > > "external makefile project"? I would prefer to build it using the > > "standard" make system so that it fits with the general scheme of things. > > > > So far, I'm having no luck figuring this out. All I get at this point is > > 'Error: Program "make" not found in PATH". > > Maybe I'd have better luck with Contiki since it is "officially" > supported > > by TI. Though there's not much eveidence to support that... > > > > I'm stuck and need to make progress. > > > > On Fri, Jun 24, 2016 at 5:49 AM, malo <[email protected]> wrote: > >> > >> Hello Clark, > >> > >> I'm happily building/flashing/debugging riot with windows CCS. At the > >> moment have working only some older riot code base build by TI compiler. > >> Have it working with newlib and 20 bits support as well. The problem is > that > >> is ugly, since TI compiler does not support naked functions and have to > move > >> SP manually at few places. > >> Nevertheless I have 6lowpan host - atmel RF233 attached to msp430f2618 > >> with coap server on top working with RPI2 on other side . > >> > >> The plan is to move to GNU compiler and make official 20bits/newlib > >> support. At the mo have msp-exp430f5529lp on my table - that could be > nice > >> kit for the official port. > >> > >> I'm not aware of any documents how to build riot with CCS (was not > >> searching that hard) but in general I just took core files one by one > and > >> defined few macros to make it happy. After had the core working just > added > >> networking and radio driver. > >> > >> wbr > >> malo > >> > >> On 20 June 2016 at 15:59, Clark Leach <[email protected]> wrote: > >>> > >>> Nothing? Really? > >>> > >>> On Tue, Jun 14, 2016 at 2:43 PM, Clark Leach <[email protected]> > >>> wrote: > >>>> > >>>> I am intersted in developing with RIOT for a few different TI targets > >>>> and have Code Composer Studio installed on Windoze 8.1 which I have > used for > >>>> several projects. Since CCS already has all the tool chains and > debugger > >>>> interfaces, it seems like it would make sense to use it for these > projects > >>>> as well. > >>>> > >>>> Is there any hope of making such a configuration work? Is there any > >>>> guidance available? I have read the howto on using Eclipse and found > the > >>>> information lacking and, at times, incomprehensible (what is a > "speaking > >>>> Variable Name", anyways). > >>>> > >>>> Any feedback would be appreciated. > >>>> > >>> > >>> > >>> _______________________________________________ > >>> devel mailing list > >>> [email protected] > >>> https://lists.riot-os.org/mailman/listinfo/devel > >>> > >> > >> > >> _______________________________________________ > >> devel mailing list > >> [email protected] > >> https://lists.riot-os.org/mailman/listinfo/devel > >> > > > > > > _______________________________________________ > > devel mailing list > > [email protected] > > https://lists.riot-os.org/mailman/listinfo/devel > > > _______________________________________________ > devel mailing list > [email protected] > https://lists.riot-os.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list [email protected] https://lists.riot-os.org/mailman/listinfo/devel
