propgcc now in the Parallax github
David Betz
Posts: 14,516
Several people have noted that Google Code will be shutting down shortly. In preparation for that, I've migrated the propgcc repository from Google Code to the Parallax github account.
https://github.com/parallaxinc/propgcc
I'd like to consider the Google Code propgcc repository to be read-only at this point but there doesn't seem to be a way to do that.
Thanks to SwimDude0614:
Here are 6 useful links. These will always download the latest version of each artifact and work with wget
GCC4
x86-64 Linux
RPi
Win32
GCC5
x86-64 Linux
RPi
Win32
https://github.com/parallaxinc/propgcc
I'd like to consider the Google Code propgcc repository to be read-only at this point but there doesn't seem to be a way to do that.
Thanks to SwimDude0614:
Here are 6 useful links. These will always download the latest version of each artifact and work with wget
GCC4
x86-64 Linux
RPi
Win32
GCC5
x86-64 Linux
RPi
Win32
Comments
For anyone curious, I will soon be attempting to throw propgcc into a continuous integration server (TeamCity). I can't promise it will be successful, but this seemed like an appropriate place to mention it. If/when I get propgcc building successfully, we should have up-to-date versions of windows, linux and raspberry pi builds.
the triggers are highly configurable. i have propware's set for a "sleep period" of 5 minutes. so you have 5 minutes to make a second, related commit before the build actually kicks off
From Here:
https://help.github.com/enterprise/2.0/admin/articles/moving-a-repository-from-github-com-to-github-enterprise/
Thanks Bob!
Anytime. I'll C you over in the SimpleIDE threads any day now. It's time for me to try it
pull request: https://github.com/dbetz/propgcc/pull/72
It wouldn't have worked for cross-compilation, and I found files where /opt/parallax was hardcoded instead of using the PREFIX environment variable (lib/build.sh and loader/build.sh for instance).
they're in the pull request linked above.
great! i have lots of disk space on the server and 16 cores @ 2.6 GHz, so bring it on! we'll have binaries of everything
David,
This may help with the propgcc Wiki: https://github.com/ArcBees/arcbees-tools/tree/master/googlecode_wiki_to_github_markdown
dgately
https://github.com/dbetz/propgcc/blob/master/loader/Makefile
If that's the case, I'll create another pull request that changes line 215 to use ${TARGET}/bin/${SPINCMP} instead of ${SPINCMP}
http://david.zemon.name/downloads/propgcc-linux-64.tar.gz
Still working on getting RPi builds succeeding.
Windows build has to wait til tomorrow. Ran of disk space tonight
I do not yet know how I'll be building 32-bit linux distros
Nice setup for TeamCity! Glad you like it.
Enjoy!
Mike
http://david.zemon.name/downloads/propgcc-win-32.zip
Are you building the default branch or release_1_0 or both?
At the moment, default (which I assume means master really). release_1_0 is on my mental to-do list, but I want to get rpi building first.
Still worried about 32-bit linux though
I eagerly await the new version
Hoping to get rpi live soon. Will update soon as it is
I don't get it. It's looking for a directory called ncurses in the source files.... but there's definitely no ncurses directory in the repository. I thought maybe I just didn't have an environment variable set correctly, or was missing a dependency, but the Makefile doesn't show any obvious issues (referring to line 254: https://github.com/DavidZemon/propgcc/blob/master/Makefile#L254). The one odd thing I noticed was that the target "$(BUILD)/ncurses/ncurses-configured" depends on "$(BUILD)/ncurses/ncurses-created" which doesn't exist in that file. So... maybe ncurses-created is supposed to create the ncurses directory? Makes sense based on the name. Where's that target defined?
--edit--
grep just finished searching the source directory and found nothing