On 19-Mar-08, at 2:32 PM, Manfred Bergmann wrote: > Eh, svn:external?
svn:externals let you reference other repositories, when you check out one, you get the other this is how you would do it sword_mac_build> svn propedit svn:externals . (not the dot for current directory)... and put in the file: sword-1.5.10 https://crosswire.org/svn/sword/tags/sword-1-5-10/ the first bit is the local folder, the second bit is the url to the other repo (this being the tag) svn:externals would be especially useful if you were working against the trunk of Sword, and/or wanted the option of committing changes back to Sword itself. otherwise... > There is a folder sword_mac_build where you just need to call: > make -f Makefile_default build-release-fat (not exactly sure about the > target name) > > That's all. That works quite smoothly... the README in the root just was outdated, so I updated it. [38] not build-debug-fat?? I skipped the make install_config & make register steps that the build mentioned. Maybe I shouldn't have, as I'm getting something a little funky.. could also be related to MacSword trunk or something else. I only have one Module installed... ESV. The book drop down is in Hebrew for some reason, and it's not functioning. > Eloquent is the name of the new Project which is hosted on Google > Code: > http://code.google.com/p/eloquent > > But as we said, it would be good to change the name to MacSword 2 or > something. And I will move the things to the SourceForge MacSword > repository. > The trunk of Eloquent project is currently only a module installer > based on a cleaned up port to Objective-C 2.0 of the MacSword SWORD > backend classes. I added some new classes for install sources and > such. > > wrapper, own Framework. Well, yes. I tried it but the current MacSword > wrapper is not capsulated enough. It accesses many other things which > it shouldn't . So first some more cleanup is needed. > But actually I would like to do this for MacSword 2, not for the > current version. Makes sense. If we can keep garbage collection optional for that lower level, it'll work for an iPhone port which would be pretty cool :-). >>> Do you use macsword-develop and macsword-user lists? > > I created them a couple of months ago but actually never posted to > them. > But of course they can be used. > And for internal development they IMO should be used at least the > developer mailing list. We certainly could... though I don't mind talking here, if nobody else minds. Having Troy and others chime in with a helpful tidbit is always good. > Yep, Core Animation for example. Actually I didn't see it in action. > But also the nice Dashboard like floater windows are really cool. Ah, yes... the HUDs (heads-up-displays)... esp. for full-screen. > There is the tag for 1.3.1 which supports Panther. > The old trunk was a 1.3beta version, Will tried to merge something > from the branch that I created into the trunk a long time ago. > So I tagged this 1.3beta before I moved the branch to the trunk. This > one still has the Lucene stuff. > And there are also still some 1.2.1 sources around. > But actually the only version I can think of back porting anything or > doing critical bugfixes is 1.3.1. > If someone is still using Jaguar than it is time to upgrade. > So on the web site we will end up with three version available: - 1.2.1 for Mac OS X 10.2 Jaguar - 1.3.1 for Mac OS X 10.3 Panther and 10.4 Tiger - and eventually the new Leopard-only version I imagine we should have some clean ups and do a 1.5 before a total UI overhaul for 2.0. baby steps SF is pretty strict... even donations need to be through their system (if we still want to keep that button... they take 5% + PayPal's fees). - nathan --- Nathan Youngman Email: nj at nathany dot com Web: http://www.nathany.com _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
