boost port file does not properly include isysroot

[James Gregurich]

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.


So, you are giving this lecture to the wrong guy. I voluntarily donated multiple weeks of expensive engineering time to macports to make it suitable for commercial developers on MacOSX and iOS.   I got NOTHING for that work….not even a "thanks for your efforts, but we really aren't interested."


 The time I spent learning and modifying the internals of mac ports showed me that there was no TECHNICAL reason why macports couldn't support the necessary options to handle commercial development. In fact, most of the work was already done…it was just incomplete. The reasons why the work is incomplete has to do with the attitudes and interests of the maintainers.  that's fine. You guys have every right to be disinterested in commercial developers if you choose.  But, I will say this…the majority of the developer action on Apple platforms is in commercial development….not unix nerds tinkering with KDE builds or server farm maintainers with fixed installations that rarely change. So, if you want your work actually used en masse, then perhaps commercial developers should be a more important audience.

 
As for me personally, after I have seen that you guys simply aren't interested in commercial development, I'm making my plans to ditch mac ports in my work flow at some convenient time. I've been doing what I can to lobby Apple to create an official, properly maintained ports collection. I have no idea if Apple has any interest in that, but it doesn't hurt to ask.


Finally, I didn't write in to "complain." I wrote in AS A COURTESY to tell you that the next Xcode beta breaks some of your code and tell you exactly what needed to be fixed. If you don't care, that's fine with me. I can hack my personal install to make it work for me in the short term to get what I need done for now. At least I can get some good out of all that time I spent working on macports.



On Jan 30, 2012, at 1:59 PM, Daniel J. Luke wrote:

> On Jan 30, 2012, at 4:47 PM, James Gregurich wrote:
>> What's the point to this comment?
> 
> perhaps you're using the wrong tool...
> 
> MacPorts is (according to the website):
> 
> "an open-source community initiative to design an easy-to-use system for compiling, installing, and upgrading either command-line, X11 or Aqua based open-source software on the Mac OS X operating system."
> 
> No where do I see "support for commercial development" as something the project claims to be targeting.
> 
> Maybe MacPorts is good for that, maybe you can contribute fixes (or at least bug reports) to help make it useful there.
> 
> Or you can complain that it doesn't work they way you want it to and threaten to go away. I don't think that's a useful way to motivate volunteers to help you, but you are of course free to try whatever you think will work.
> 
>> On Jan 30, 2012, at 11:47 AM, Daniel J. Luke wrote:
>>> On Jan 30, 2012, at 2:16 PM, James Gregurich wrote:
>>>> then people must not be using macports for commercial development because there is no way commercial developers can drop 10.6 support yet.
>>>> 
>>>> given the time I have wasted trying to contribute to this project, I'm not inclined to spend any more time figure out how to file bug reports on it. I've made the problems known to you guys. handle them as you wish. I'm resigned to eventually going back to manually building my libs as I don't see this project as having a significant future.
>>> 
>>> my can opener is bad at driving nails, too.
> 
> 
> --
> Daniel J. Luke                                                                   
> +========================================================+                        
> | *---------------- dluke at geeklair.net ----------------* |                          
> | *-------------- http://www.geeklair.net -------------* |                          
> +========================================================+                        
> |   Opinions expressed are mine and do not necessarily   |                          
> |          reflect the opinions of my employer.          |                          
> +========================================================+
> 
> 
>