Page 1 of 1

Chicken and egg: xTIMEcomposer and GitHub

Posted: Thu Jul 20, 2017 8:15 am
by aclassifier
To have code on GitHub, what's the procedure?

Copy my present xTIMEcomposer project to GitHub and then import it back to a new xTIMEcomposer project?

Or is there some way to just connect (clone "up") GitHub to my existing xTIMEcomposer project?

I want to commit to local and push to GitHub I assume. The code would be open.

Is this described anywhere?

I have imported libraries from XMOS directly in xTIMEcomposer, but also downloaded the zipped projects from XMOS app notes. But they don't seem to be on GitHub(?)

I found some info at http://www.xcore.com/viewtopic.php?f=26 ... hop#p16706

Re: Chicken and egg: xTIMEcomposer and GitHub

Posted: Wed Jul 26, 2017 3:16 pm
by xsamc
The source for most (but not all) app notes can be found in the "examples" directory of the relevant library repository on github.com/xmos, rather than as separate repos for each note.

To ease the versioning of your own code, I'd suggest that you structure your application such that it is in separate directories to the libraries you have downloaded from XMOS. This way you can easily initialise these directories as git repositories and push them to github. I believe that if you start by creating a new repository through the github website, but do not add any of the default files they suggest to it, you can then follow these instructions.

Cheers,
Sam

Re: Chicken and egg: xTIMEcomposer and GitHub

Posted: Thu Jul 27, 2017 8:52 am
by aclassifier
Thanks, Sam!

The libraries- I have also downloaded them on the GitHub site as | Clone or download | Download zip|. But I guess, then it's harder to keep them updated as you update them? Should I have used | Open in desktop | instead? In the latter case, from the GitHub desktop, how do I then connect that directory to my xTIMEcomposer project? I have done it on some (both from XMOS and Adafruit, but the XMOS stuff is in an XMOS directory, not the xTIMEcomposer project). If you look at my projects and libraries there seems to be some categories (rather messy without much clear thoughts before on these issues):

Image
  • My projects that I do have local commits on, like _Aquarium_1_x [_Aquarium_1_x master]
  • My projects that I don't have local commits on, like xmos_issues (nothing here)
  • XMOS libraries that I have copied as source files a couple of years ago (I think), like module_i2c_master [sc_i2c]
  • XMOS libraries that I have cloned from inside xTIMEcomposer, like lib_i2c [lib_i2c - 4.0.0] This type comes with version string, indicating that it's kept(?) in sync with GitHub?. But if I look at https://github.com/xmos/lib_i2c I see it's updated recently, but that in the examples directory the commit is older. How do I ensure that I have the latest version?
Is there anything I should have done with my XMOS stuff as you see it? Delete them all and start using the same procedure for all? And in case, which procedure? I haven't edited in any of them.

If I follow the procedure that you pointed out, will I then both commit and push inside xTIMEcomposer? I assume so. But if I use GitHub Desktop in addition, does this in any way clutter that recipe?

There seems to be quite many alternatives here, and when I don't really know what's under the hood I end up being quite confused.

Re: Chicken and egg: xTIMEcomposer and GitHub

Posted: Tue Aug 15, 2017 2:47 pm
by aclassifier
I am trying to find out where to pick SW for running the WiFi sliceCARD via a breakout board on the xCORE-200 eXplorerKIT.

When I download a packet from GitHub it may contain several modules and apps plus the extra outer files Makefile, LICENSE.txt, README.rst, xpd.xml and CHANGELOG.rst.

However, when I import the modules and apps to xTIMEcomposer only the modules and apps are imported and the extra outer files seem to be lost.

It this a correct description? If so, why (not)?

See http://www.teigfam.net/oyvind/home/tech ... he_drivers point 1.7 and 2.5.