Fred, I have been the main contributor to pbxbuild since it was originally written Hans Baier. Hans did excellent work for a first attempt so, none of what follows is meant to be a bad commentary on any of that. In fact, working on pbxbuild, gave me some insight on how to do the new tool. I've tried hard to make it general purpose, but pbxbuild is not suited to building many project types.
The changes up until my reversion didn't work at all in many cases. I have consistently had to roll back this code to r29000 in order for it to work properly. My commit message wasn't mean the way you interpreted it. It was meant to express that what was on HEAD *prior* to my rollback was broken, not to state that I was breaking the code and that everyone should join me on the other tool. The fact that you would think that, surprises me. The pbxbuild tool is horribly broken in so many respects that it hardly matters whether I revert or not at this point because I will surely break things for one person or for another person no matter what I do. I thought I was doing the right thing by reverting it to 29000 so that it could be useful to more people, but as I said in my previous statement it's pointless trying to fix it because it's whole paradigm is wrong. It tries to gather information from the various phases of the build and compose a GNUmakefile it. A good analogy for this tool is, basically, that of a compiler which can only build a limited set of programs, most of which closely resemble "Hello, World." The reason I took a unilateral approach to pbxbuild was for the following reasons: 1) I am the only one, to my knowledge, maintaining the thing... look at the changelog and the commit history. 2) I can demonstrate that it is broken for most modern xcodeproj files because of recent changes. 3) I felt as though the revision I moved it back to was for the best. I seldom have an "attitude" regarding anything I do and I'm really very hurt that you often seem to feel otherwise. Additionally, I'm grieved that you won't consider helping with a better tool because I'm the one developing it. I don't usually make unilateral decisions on something unless I'm the only one working on it. If someone else is working with me... I consult the group. In any case pbxbuild is a clumsy approach to solving the problem of building apps from xcodeproj files. It tries VERY unsuccessfully to generate GNUmakefiles. It does work in some simple cases, but fails for most others. The new tool I'm developing doesn't have these shortcomings because it doesn't rely on gnustep-make, nor does it rely on GNUmakefiles. Neither of these things are bad technologies, but the translation from xcodeproj files to GNUmakefiles is fraught with difficulty. The new tool directly interprets the build phases in the project file and handles them as the xcodebuild tool on the Mac would. Anyway... I will only be making critical fixes to pbxbuild from this point on, thus, it is deprecated unless someone else feels like taking it up. I may, at some point, add the capability to the new tool (buildtool...needs a better name) to generate GNUmakefiles, thus completely superceding pbxbuild... but this is not my top priority with the new tool Sincerely, GC On Fri, Mar 9, 2012 at 4:25 AM, Fred Kiefer <[email protected]> wrote: > On 09.03.2012 01:05, Gregory Casamento wrote: >> >> Guys, >> >> The pbxbuild program is now deprecated. In spite of the fact that it >> does work in many cases, it has already been superceded in >> functionality by the buildtool/xcode framework I've been writing which >> builds projects in the same way the xcodebuild tool does on mac os x, >> through direct interpretation of the .xcodeproj file without any need >> for GNUmakefiles. >> >> I urge people not to depend on pbxbuild any longer and for people to >> look at the new buildtool/xcode framework which I will be releasing in >> the next few weeks. >> >> Thanks, GC > > > Greg, > > could you please explain this step? Together with your strange commit > message for pbxbuild this rather sounds like: "I broke your toy, you now > have to play with mine". And this isn't that attitude I like to see in a > free software project I am contributing to. > > I am using pbxbuild on a weekly basis and the current code, before your > latest change, worked rather well for me. It may well be that the new build > tool is superior to pbxbuild, but why did you have to make a revert on > pbxbuild to prove this? > > Last summer you made a similar revert and than rolled back this revert and I > had to clean up after that. I wont do this again now. Either the new build > tool works for me, or I will have to write a GNUmakefile manually for each > Mac project I port over to GNUstep. What I don't intend to do is work on the > new build tool as our different approaches to participative software > development don't seem to fit. > > Fred > > _______________________________________________ > Gnustep-dev mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/gnustep-dev -- Gregory Casamento Open Logic Corporation, Principal Consultant yahoo/skype: greg_casamento, aol: gjcasa (240)274-9630 (Cell) http://www.gnustep.org http://heronsperch.blogspot.com _______________________________________________ Gnustep-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnustep-dev
