More replies for you ;-) ! Le 13 févr. 2011 à 00:23, yokull a écrit :
> > thnx 4 the reply rob > >> • the wiki build instructions provide the correct process and behaviour >> for building quicksilver, but the instructions (and many notes) do not. what >> is the story here? i can make the necessary changes to my fork and push >> them. is this fine, or is there something else going on i need to be made >> aware of? > > Which are wrong? The ones in the README with the source? > > hmmm, ya i was referring to the README on github > but realized i still had build settings from > http://qsapp.com/wiki/Building_Quicksilver > didn't try to do a "build & run" right after a fresh clone, but i think the > xcode build settings were already properly config'd for that > > i also assumed that README was out of date It should be. I've updated them after the repo was moved. Re-reading it I guess the only missing things are a link to qsapp.com site & wiki. > is the "a few notes on working with git" still valid? IIRC I stopped bltrversion (the script used by the build system to update plugins bundle's versions) from tinkering with the plists files, on the basis that the developer is more aware of releases that some dumb script. So the point is moot in the current master branch. > are there any issues still outstanding here? The only issue left for me is ("hacked" by https://github.com/quicksilver/Quicksilver/commit/cee37f05c4e500691b969bb76097fc514553ce34) that I had to tweak the Xcode projects because of some kind of bug in Xcode with having projects dependent on projects dependent on the master project. This means you need to Build two times after a Clean (or the first time) to get the Quicksilver.app application to build. An easy fix would be to move all "core" Core, Finder, Bezel, Primer, Hotkeys) into targets of the main project. > does it look like "git submodules" might be helpful with this? > i'm unsure about the svn side-effects here... > >> • is anyone making available (or intending to make) regular alpha >> builds? this would be a valuable resource in getting people >> re-excited/re-kindled with qs if FREQUENT developments are provided to the >> public. it would be a VERY welcome change in contrast to the history of qs >> silence > > Can’t answer that. I think it will all become easier when the update system comes back under our control ;-). The update level stuff ought to take care of all this (you can declare "release", "prerelease" (a.k.a beta) or "developer", so people could use the features (and crashes ;-)) they want. > >> • if regular builds are to be offered (i can potentially provide this), >> what are the target architectures/systems for qs? 10.4? 10.6 and up only? >> ppc? hackintosh on vic-20? > > 10.5+. I would say Intel-only unless someone objects. If we can make sure QS runs on 10.5, then fine, but 10.7 might not be too far away, so it looks more logical to me to stick with 10.5 (until some rewrite gain enough traction ;-)). > i just tried out latest gold-master of xcode4 as well, and apparently it's > not including the 10.5 SDK > just made a build and seems good so far > not sure if there are any 10.5 dependencies, or anything using 10.5 that can > be dropped in order to improve performance, etc. That's not a good thing. Personally I guess I'll wait for 10.7 (or Xcode 4) to come out before thinking about it. -- Etienne Samson [email protected]
