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
Processes: 73 total, 3 running, 70 sleeping, 388 threads 07:58:53 Load Avg: 0.22, 0.39, 0.34 CPU usage: 1.58% user, 1.71% sys, 96.70% idle SharedLibs: 7508K resident, 784K data, 0B linkedit. MemRegions: 27149 total, 1325M resident, 26M private, 532M shared. PhysMem: 804M wired, 2062M active, 748M inactive, 3614M used, 472M free. VM: 196G vsize, 1033M framework vsize, 1429432(41) pageins, 56177(0) pageouts. Networks: packets: 4048303/3574M in, 4129641/2714M out. Disks: 26117292/217G read, 1553583/55G written. PID COMMAND %CPU TIME #TH #WQ #POR #MREGS RPRVT RSHRD RSIZE VPRVT 96916 top 5.8 00:02.25 1/1 0 24 33 1220K 264K 1800K 17M 96831 ugslmd 0.0 00:13.48 3 0 28 41 18M 244K 19M 49M 96803 mdworker 0.0 00:01.15 3 1 52 96 4904K 18M 11M 81M 77870- PackageMaker 0.0 04:20.72 3 1 408 401 38M 104M 62M 105M 77177 WebProcess 0.0 15:35.19 7 2 124 356 27M 47M 51M 250M 72350 bash 0.0 00:00.25 1 0 17 25 292K 856K 864K 17M 72349 login 0.0 00:00.02 1 0 22 53 120K 312K 788K 19M 58247 VDCAssistant 0.0 00:00.32 5 2 93 89 712K 18M 3496K 80M 58245- Skype 0.0 00:35.39 19 2 314 365 43M 81M 44M 198M 57970 Safari 0.0 00:08.43 12 2 185 345 11M 76M 22M 236M 57861- dbfseventsd 0.0 00:19.33 1 0 8 26 12K 304K 128K 12K 57860- dbfseventsd 0.0 00:30.89 1 0 8 26 4136K 300K 4272K 12M 57859- dbfseventsd 0.0 00:04.12 1 0 14 25 16K 296K 240K 5184K 57849 Image Captur 0.0 00:00.50 3 2 83 88 1824K 35M 5236K 87M 57831- Dropbox 0.0 04:01.27 27 2 196 627 60M 51M 44M 260M 57776 bash 0.0 00:00.06 1 0 17 25 260K 856K 800K 1a 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.
Processes: 94 total, 9 running, 85 sleeping, 421 threads 08:03:04 Load Avg: 3.29, 1.34, 0.71 CPU usage: 35.11% user, 8.80% sys, 56.7% idle SharedLibs: 7508K resident, 784K data, 0B linkedit. MemRegions: 27787 total, 1490M resident, 27M private, 625M shared. PhysMem: 818M wired, 2245M active, 861M inactive, 3924M used, 162M free. VM: 243G vsize, 1033M framework vsize, 1435350(12) pageins, 56177(0) pageouts. Networks: packets: 4048690/3574M in, 4130201/2714M out. Disks: 26124670/217G read, 1577493/55G written. PID COMMAND %CPU TIME #TH #WQ #POR #MREGS RPRVT RSHRD RSIZE VPRVT 97240 taskgated 0.6 00:00.08 3 0 44 41 700K+ 244K 1276K+ 81M 96923 sh 0.0 00:00.01 1 0 14 24 316K 852K 836K 17M 96916 top 7.8 00:17.71 1/1 0 46+ 33 1344K 264K 1924K 17M 96831 ugslmd 0.0 00:13.50 3 0 28 46 18M 244K 19M 68M 96803 mdworker 8.2 00:07.60 3 1 56 186 14M+ 20M 29M+ 98M 83432 cc1 0.0 00:00.11 1/1 0 14+ 50+ 12M+ 7156K+ 15M+ 84M+ 83431 i686-apple-d 0.0 00:00.00 1 0 14+ 34+ 328K+ 460K+ 784K+ 82M+ 83430 llvm-gcc-4.2 0.0 00:00.00 1 0 14+ 22+ 144K+ 284K+ 400K+ 73M+ 83425 cc1 0.0 00:00.13 1/1 0 14+ 53+ 15M+ 7156K+ 18M+ 87M+ 83424 i686-apple-d 0.0 00:00.00 1 0 14+ 34+ 328K+ 460K+ 784K+ 82M+ 83423 llvm-gcc-4.2 0.0 00:00.00 1 0 14+ 22+ 144K+ 284K+ 400K+ 73M+ 83418 cc1 0.0 00:00.17 1/1 0 14+ 61+ 21M+ 7156K+ 25M+ 93M+ 83417 i686-apple-d 0.0 00:00.00 1 0 14+ 34+ 328K+ 460K+ 784K+ 82M+ 83416 llvm-gcc-4.2 0.0 00:00.00 1 0 14+ 22+ 144K+ 284K+ 400K+ 73M+ 83392 cc1 0.0 00:00.38 1/1 0 14+ 85+ 43M+ 7156K+ 47M+ 115M+ 83391 i686-apple-d 0.0 00:00.00 1 0 14+ 34+same with ./jbuild.sh 6 rm -all
Processes: 91 total, 6 running, 85 sleeping, 404 threads 08:06:53 Load Avg: 4.48, 2.60, 1.37 CPU usage: 72.76% user, 4.80% sys, 22.42% idle SharedLibs: 7504K resident, 784K data, 0B linkedit. MemRegions: 28044 total, 1525M resident, 26M private, 698M shared. PhysMem: 806M wired, 2367M active, 711M inactive, 3883M used, 205M free. VM: 236G vsize, 1033M framework vsize, 1442627(7) pageins, 57238(0) pageouts. Networks: packets: 4049506/3575M in, 4131380/2714M out. Disks: 26129240/217G read, 1601440/56G written. PID COMMAND %CPU TIME #TH #WQ #POR #MREGS RPRVT RSHRD RSIZE VPRVT 96916 top 8.5 00:34.73 1/1 0 47 34 1604K 264K 2180K 17M 96831 ugslmd 0.0 00:13.51 3 0 28 47 18M 244K 19M 68M 96803 mdworker 0.2 00:14.19 3 1 56 207 16M 18M 31M 101M 84180 sh 0.0 00:00.00 1 0 14 24 312K 852K 836K 17M 77870- PackageMaker 0.0 04:20.72 3 1 408 401 34M 104M 57M 105M 72995 cc1 0.0 00:00.42 1/1 0 14+ 80+ 38M+ 7156K+ 42M+ 110M+ 72994 i686-apple-d 0.0 00:00.00 1 0 14+ 34+ 328K+ 460K+ 784K+ 82M+ 72993 llvm-gcc-4.2 0.0 00:00.00 1 0 14+ 22+ 144K+ 284K+ 400K+ 73M+ 72988 cc1 0.0 00:00.52 1/1 0 14+ 75+ 37M+ 7156K+ 44M+ 106M+ 72987 i686-apple-d 0.0 00:00.00 1 0 14+ 34+ 328K+ 460K+ 784K+ 82M+ 72986 llvm-gcc-4.2 0.0 00:00.00 1 0 14+ 22+ 144K+ 284K+ 400K+ 73M+ 72966 i686-apple-d 0.0 00:00.00 1 0 14 34 328K 460K 784K 82M 72965 llvm-gcc-4.2 0.0 00:00.00 1 0 14 22 144K 284K 400K 73and just for grins ./jbuild.sh 8 rm -all
Processes: 102 total, 3 running, 8 stuck, 91 sleeping, 417 threads 08:11:42 Load Avg: 5.37, 3.53, 2.09 CPU usage: 92.49% user, 6.82% sys, 0.68% idle SharedLibs: 7504K resident, 784K data, 0B linkedit. MemRegions: 28490 total, 1629M resident, 26M private, 871M shared. PhysMem: 807M wired, 2474M active, 638M inactive, 3919M used, 169M free. VM: 262G vsize, 1033M framework vsize, 1458600(0) pageins, 66437(0) pageouts. Networks: packets: 4049722/3575M in, 4131633/2714M out. Disks: 26136332/217G read, 1645731/57G written. PID COMMAND %CPU TIME #TH #WQ #POR #MREGS RPRVT RSHRD RSIZE VPRVT 96916 top 9.2 00:54.89 1/1 0 54 34 1680K 264K 2256K 17M 96831 ugslmd 0.1 00:13.53 3 0 28 47 18M 244K 19M 68M 96803 mdworker 0.3 00:24.31 3 1 56 265 26M 18M 34M 109M 94051 cc1 0.0 00:00.34 1 0 14+ 68+ 28M+ 7156K+ 32M+ 100M+ 94050 i686-apple-d 0.0 00:00.00 1 0 14+ 34+ 328K+ 460K+ 784K+ 82M+ 94049 llvm-gcc-4.2 0.0 00:00.00 1 0 14+ 22+ 144K+ 284K+ 400K+ 73M+ 94046 cc1 0.0 00:00.34 1 0 14+ 67+ 28M+ 7156K+ 32M+ 100M+ 94045 i686-apple-d 0.0 00:00.00 1 0 14+ 34+ 328K+ 460K+ 784K+ 82M+ 94044 llvm-gcc-4.2 0.0 00:00.00 1 0 14+ 22+ 144K+ 284K+ 400K+ 73M+ 94037 cc1 0.0 00:00.43 1 0 14+ 68+ 31M+ 7156K+ 37M+ 101M+ 94036 i686-apple-d 0.0 00:00.00 1 0 14+ 34+ 328K+ 460K+ 784K+ 82M+ 94035 llvm-gcc-4.2 0.0 00:00.00 1 0 14+ 22+ 144K+ 284K+ 400K+ 73M+ 94030 cc1 0.0 00:00.56 1 0 14+ 77+ 39M+ 7156K+ 46M+ 109And 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.