Re: boost port file does not properly include isysroot

[James Gregurich]

Did the last message in the thread escape your notice? Did Landon download the work, look at it and give me feedback like I asked?  I only know of one person who did that…and it wasn't Landon. It wasn't hard, all you had to do was download the zip file, unpack it to the root directory and invoke 'port' commands on it. I would have taken a few hours of time for an experienced developer to review the changes and comment on the appropriateness of the changes…perhaps make recommendations alternative approaches or additional work that needed to be done. If someone had told me, "yes, this looks good. we are interested in this work, but we need the following additional work done….or do it some other way" I would have made the additional effort.   As for submitting a diff now…. this work is a year out of date. It would probably need to be started from scratch given the project's code has likely evolved significantly since then. I still have the zip file some where on my system, but I'm busy with other things. I have no time to spend on this effort any more. If someone else wants the work and wants to pick up the ball and run with it, he can have the zip file. But I've moved on.   Again I make the statement….  I didn't come here to complain that my work wasn't accepted. It was merely answering Daniel's point that I should make effort to update the system. I did make that effort. iOS cross compiling support   by James Gregurich Jan 24, 2011; 06:37pm :: Rate this Message:    - Use ratings to moderate (?) Reply | Print | View Threaded | Show Only this Message hi.  I've done the proof-of-concept work on extending macports to handle cross-compiling so that it can be used to maintain 3rd party libs for iOS development. I have successfully built ICU against the iPhone sdk and have it running in the debugger on an iPad.  I'd like to turn this work over to a macports developer to be vetted, completed and merged into the mainline build in an appropriate fashion. I didn't know much about the internals of macports and I didn't known anything about TCL. I figured out most of the details as I went along. I'd like to turn the work over to someone more qualified than I am in scripting langauges and macports to complete the project.  Is there any interest of the part of the macports developers in accepting the work?  NOTE: I did not use your version control system. I modified the scripts in place after the system was installed. I can provide a list of the files I changed and some explanation on what was changed. I basically attempted to piggy-back target/host support on top of the existing variables without changing their function. The approach is fine for proof-of-concept, but the the underlying variables such as os.version and such should be modified and/or renamed to make the design cleaner. However, that task should be done by someone who knows the internals very well and who knows how the changes will affect existing ports.  I did have to modify the ICU port file because it has some custom steps that need to be done before its configure script will succeed for a cross-compile. I also had to make an adjustment because of the lack of tzfile.h in the target OS.  -James  On Jan 30, 2012, at 3:15 PM, Bradley Giesbrecht wrote: On Jan 30, 2012, at 2:30 PM, James Gregurich wrote: As you will recall from a year ago, I've already done that. I gave you guys a complete working prototype that had support for clang, customization of  universal binary architectures, and the comprehensive ability to target different SDKs. I had 5 or 6 ports (including complex ones such as boost) building simultaneously for MacOSX and iOS as universal binaries on both. only one person ever cared enough to look at it. Landon expressed interest at the time and requested a unified diff. http://old.nabble.com/iOS-cross-compiling-support-td30754615.html If you have an svn tree and your changes are in base do this from trunk: $ svn diff base > patch-macports-base-cross-compile-support.diff Then attach it to a new ticket at: http://trac.macports.org Regards, Bradley Giesbrecht (pixilla) _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev