Yeah no worries. Happy to do it. We need the right build out there. Thanks for the quick tip.
Let's hope this one works okay for Baggers. I guess we need to figure out how to handle this for official releases since I imagine we want our code to work on Snow Leopard as well as Lion and Mountain Lion. Did you ever try the Mac release I posted on Google Code? Did that fail on your Snow Leopard system like it did for Baggers?
I think I did, if we are talking about the same one. That was the release I worked through the permissions issue on. (xattrib) When I realized the build was newer than my OS, I started down this road to build a nice old package.
Seems to me, this comes down to either:
1. Build on an older OS X release. Could do this in a VM maybe. I've not run OS X that way before.
2. Modify the build scripts to pass along that argument needed to limit the executable.
FWIW, anybody building on Windows 8 will encounter a similar thing with binaries that won't run on XP. Baggers had it happen with P2Prep. First build was on Windows 7, ran fine, second build was on Win 8, no more XP...
For a while, I can make packages. This isn't hard now. Honestly, I'm kind of tempted to try packaging one up into one of those spiffy Apple installer type distributions.
I think I did, if we are talking about the same one. That was the release I worked through the permissions issue on. (xattrib) When I realized the build was newer than my OS, I started down this road to build a nice old package.
Seems to me, this comes down to either:
1. Build on an older OS X release. Could do this in a VM maybe. I've not run OS X that way before.
2. Modify the build scripts to pass along that argument needed to limit the executable.
FWIW, anybody building on Windows 8 will encounter a similar thing with binaries that won't run on XP. Baggers had it happen with P2Prep. First build was on Windows 7, ran fine, second build was on Win 8, no more XP...
For a while, I can make packages. This isn't hard now. Honestly, I'm kind of tempted to try packaging one up into one of those spiffy Apple installer type distributions.
If you're willing to figure out how to make an Apple installer for PropGCC that would be great! I think Steve (jazzed) has done some work on this for SimpleIDE so he might be able to point you in the right direction.
For a while, I can make packages. This isn't hard now. Honestly, I'm kind of tempted to try packaging one up into one of those spiffy Apple installer type distributions.
I asked my good neighbour if I could use their net for a while, and grabbed the Mountain Lion update, as my hub wouldn't allow a file >4GB to be downloaded
So I now have Mountain Lion on my iMac, and have David's build working, and building the sdramtest demo
Thanks all look forward to having a good play with it tomorrow after work!
I'm doing a fresh build of current default to prepare for a go at an install package and I can definitely tell the difference between jsbuild.sh 5 and 6 The latter just screams through stuff! Back above 3 for a load average.
It took about a third the time. Right about 15 minutes on this machine. The one this morning was a little over 40, just FYI. (Thanks Jazzed)
To set the system PATH on OSX starting with Leopard, you drop a file containing the path into /etc/paths.d A .bashrc script works, but is non-standard.
I used sudo echo "/opt/parallax/bin" > /etc/paths.d/PropGCC
Gonna wait a bit on a package. Built two with PackageMaker tonight and had some basic failure on both. If there is demand, I can revisit this. What we have is pretty easy right now.
I'm doing a fresh build of current default to prepare for a go at an install package and I can definitely tell the difference between jsbuild.sh 5 and 6 The latter just screams through stuff! Back above 4 for a load average.
It took about a third the time. Right about 15 minutes on this machine. The one this morning was a little over 40, just FYI. (Thanks Jazzed)
To set the system PATH on OSX starting with Leopard, you drop a file containing the path into /etc/paths.d A .bashrc script works, but is non-standard.
I used sudo echo "/opt/parallax/bin" > /etc/paths.d
Gonna wait a bit on a package. Built two with PackageMaker tonight and had some basic failure on both. If there is demand, I can revisit this. What we have is pretty easy right now.
What kind of processor do you have on your Mac and how much memory?
a few minutes into a build using ./jsbuild.sh 5 rm -all There is a point a few minutes in where it is just screaming on lots of little object files. I took the TOP snapshot at the peak during that time on each snapshot. Just rough data, but kind of interesting anyway.
And I/'m gonna let that one finish, because it peaks in the high fives, which is hard to get for a load average. Maybe too high. The fours are generally sweet, and indicate the machine is running very quickly. That one might come in under 15 minutes, depending. Edit: It actually took a bit longer. I suspect the OS got starved for CPU time on this one, clogging things more than enabing them.
**used to do a fair amount of system profiling for large data applications, and this stuff interests me some.
Today, I gotta get the USB devices sorted out so I can write some programs. This ended being a fun distraction, aside from building just to get the GCC for this Mac OS. Needed that. I will have questions. Probably embarrasing ones. lol
Going forward, I can leave this Mac all setup. If a package needs to be made, let me know. In P2 land, it's probably just me. But in P1 land, there could be older Mac computers out there. The V1.0 build that works with P1 that Steve did is in the dropbox. They all have P2load in them, but it can be ignored / removed easy enough.
One of you guys should edit the install / readme / whatever document to reflect what I learned on Mac OS. Path, permissions, etc... are handy to know for passers by who may not pick up our dialog here. I can make edits, if you tell me what document and where too. Easy enough to fetch it, add, then attach here for you guys to drop back into the mix when it makes sense.
Work finished, food eaten, kids to bed, Prop2 play time just copied the ww1024x600.bin to SD card, put it in DE2-115 board, built the wireworld c demo that David kindly ported, and it works so I can now start getting the rest of my drivers ported to work with C.
Happy days..
btw C guys, for the file handling stuff, does it have any directory stuff ported? or is it all root? and can you do findfirstfile and findnextfile?
Work finished, food eaten, kids to bed, Prop2 play time just copied the ww1024x600.bin to SD card, put it in DE2-115 board, built the wireworld c demo that David kindly ported, and it works so I can now start getting the rest of my drivers ported to work with C.
Happy days..
btw C guys, for the file handling stuff, does it have any directory stuff ported? or is it all root? and can you do findfirstfile and findnextfile?
Yes, the PropGCC file support handles directories using "/" as the separator.
The build I did works. Actually both work. Shall I add those to the downloads section? The GCC V1.0 build would interest P1 users running snow leopard or newer. It might actually run on Leopard too. I don't have a system to check and the docs I read are still unclear to me. In any case, I have that one right. It's the 1.0 release.
A bigger question is whether or not to put *any* of the interim ones for P2 up there, or just use the Dropbox for the few, if any people, interested. Thoughts.
@Jazzed, I'll find the docs and add what I learned at some point in the near future. Thanks.
BTW: I built everything just as an ordinary user. I don't know that the root build instructions are needed. Can one of you expand on that some? And Smile, this thread is kind of meandering a little, but it's where the conversation is. Point me somewhere else, if warranted.
I'm up and coding C on my P2 emulation, and I'm on a Mac. Only the task of connecting the Prop Plug to an XP VM for Pnut, and I'm set for a while, but for Win 7 code.
I don't know how to tell about the Prop Plug state like I can on a Windows machine, but P2load seems to know. I need to get detail on this. Hints? (I know, read the P2load code, and I may do just that, but would appreciate a pointer if somebody has sorted this all out.)
Thanks Baggers and David for putting a little starter code out there that would interest me. It's a big help. Now I've got to work on sucking less at C.
Comments
Filename is: PropGCC_P2_Alpha_V_1_9_0_OSX_10_6_8.tar.gz
Keep checking back. For some reason, it's a slow upload right now. 30k/sec
Seems to me, this comes down to either:
1. Build on an older OS X release. Could do this in a VM maybe. I've not run OS X that way before.
2. Modify the build scripts to pass along that argument needed to limit the executable.
FWIW, anybody building on Windows 8 will encounter a similar thing with binaries that won't run on XP. Baggers had it happen with P2Prep. First build was on Windows 7, ran fine, second build was on Win 8, no more XP...
For a while, I can make packages. This isn't hard now. Honestly, I'm kind of tempted to try packaging one up into one of those spiffy Apple installer type distributions.
Look here: https://code.google.com/p/propside/source/browse/?name=spinside#hg%2FSimpleIDE.pmdoc
So I now have Mountain Lion on my iMac, and have David's build working, and building the sdramtest demo
Thanks all
Glad you are running!
I'm doing a fresh build of current default to prepare for a go at an install package and I can definitely tell the difference between jsbuild.sh 5 and 6 The latter just screams through stuff! Back above 3 for a load average.
It took about a third the time. Right about 15 minutes on this machine. The one this morning was a little over 40, just FYI. (Thanks Jazzed)
To set the system PATH on OSX starting with Leopard, you drop a file containing the path into /etc/paths.d A .bashrc script works, but is non-standard.
I used sudo echo "/opt/parallax/bin" > /etc/paths.d/PropGCC
Gonna wait a bit on a package. Built two with PackageMaker tonight and had some basic failure on both. If there is demand, I can revisit this. What we have is pretty easy right now.
at idle, bunch of stuff launched, but not busy
a few minutes into a build using ./jsbuild.sh 5 rm -all There is a point a few minutes in where it is just screaming on lots of little object files. I took the TOP snapshot at the peak during that time on each snapshot. Just rough data, but kind of interesting anyway.
same with ./jbuild.sh 6 rm -all
and just for grins ./jbuild.sh 8 rm -all
And I/'m gonna let that one finish, because it peaks in the high fives, which is hard to get for a load average. Maybe too high. The fours are generally sweet, and indicate the machine is running very quickly. That one might come in under 15 minutes, depending. Edit: It actually took a bit longer. I suspect the OS got starved for CPU time on this one, clogging things more than enabing them.
**used to do a fair amount of system profiling for large data applications, and this stuff interests me some.
Today, I gotta get the USB devices sorted out so I can write some programs.
Going forward, I can leave this Mac all setup. If a package needs to be made, let me know. In P2 land, it's probably just me. But in P1 land, there could be older Mac computers out there. The V1.0 build that works with P1 that Steve did is in the dropbox. They all have P2load in them, but it can be ignored / removed easy enough.
One of you guys should edit the install / readme / whatever document to reflect what I learned on Mac OS. Path, permissions, etc... are handy to know for passers by who may not pick up our dialog here. I can make edits, if you tell me what document and where too. Easy enough to fetch it, add, then attach here for you guys to drop back into the mix when it makes sense.
Happy days..
btw C guys, for the file handling stuff, does it have any directory stuff ported? or is it all root? and can you do findfirstfile and findnextfile?
A bigger question is whether or not to put *any* of the interim ones for P2 up there, or just use the Dropbox for the few, if any people, interested. Thoughts.
@Jazzed, I'll find the docs and add what I learned at some point in the near future. Thanks.
BTW: I built everything just as an ordinary user. I don't know that the root build instructions are needed. Can one of you expand on that some? And Smile, this thread is kind of meandering a little, but it's where the conversation is. Point me somewhere else, if warranted.
I'm up and coding C on my P2 emulation, and I'm on a Mac. Only the task of connecting the Prop Plug to an XP VM for Pnut, and I'm set for a while, but for Win 7 code.
I don't know how to tell about the Prop Plug state like I can on a Windows machine, but P2load seems to know. I need to get detail on this. Hints? (I know, read the P2load code, and I may do just that, but would appreciate a pointer if somebody has sorted this all out.)
Thanks Baggers and David for putting a little starter code out there that would interest me. It's a big help. Now I've got to work on sucking less at C.