Re: Some general questions

[Austin Clow]

Thank you all for all your responses. I have learned a lot in the last few 
hours that reading the wiki didn't clear up for me (I have been reading it for 
months and only just got around to joining this list,  should have done it 
sooner). 

In the future, I will have many more questions later about GNUstep and getting 
my software ported over to it. And I will try to contribute where I can. I know 
that I will start to notice a lot of the differences once I get started and 
those will be reported as well.  I have been looking into the Theming that has 
started to be added to the AppKit. There is a lot of interesting stuff there. 

I do have a question: How can I make Ubuntu launch into GWorkspace/GNUstep 
instead of Unity as default? I would like to see GNUstep with out all the other 
widgets. I was wondering about the possibility of even replacing the login 
window with a GNUstep app. Just curious. 


Thanks, 
Austin 


On May 24, 2011, at 5:52 PM, Riccardo Mottola wrote:

> Hi,
> 
> other have replied already, but I want to pinpoint some details.
> 
> Austin Clow wrote:
>> 1) Products that use GNUstep libraries can still be sold?
>> 
>>   
> The general answer is yes, since they are LGPL. It depends on other details 
> and others are more expert than me.
> 
>> 2) The objlib2 runtime is the GNUstep runtime that incorporates the 'old 
>> GNUstep' runtime with Étoilé's ObjectiveC2 extension. Which makes it 
>> compatible with Apple's Runtime in specification only, but not 
>> implementation. Ergo, they are not binary compatible.
>> 
>>   
> We are not binary compatibile. That's quite tough... different architectures, 
> underlying operating systems, linkers... But we aim to be quite reasonably 
> source compatible.
>>      Questions: What is the easiest way to compile a GNUstep program in 
>> Xcode. Regardless of it being able to run on Mac OS X. (I want a GNUstep 
>> binary produced). I don't want to use Make. Really what I am asking is what 
>> is the procedure (in the terminal) to create a GNUstep binary in Mac OS X.
>>   
> There is no ready pre-baked thing for that. I know some people worked on a 
> chain. What I recommend is to set up a clean and plain gnustep system and 
> compile there, by syncing the source-code through a CVS/SVN/whatever system. 
> That's how I do maintain apps and tools which run on both systems, and I do 
> that for several. I prefer to tweak the interface anyway. The code can 
> sometimes be really 100% the same.
> 
> Many free Unices will do fine, although gnustep should work on Apple I advise 
> you to have a native one. Any major Linux should do (Debian, Gentoo, SuSE... 
> for the latter Richard Stonehouse provides excellent packages) and also 
> FreeBSD/NetBSD/OpenBSD are quite well maintained too.
> 
> 
> Another route might be to have gnustep-make to Cocoa.
> 
> Good luck with your tool. You plan to make keep it proprietary - perfectly 
> fine, but take a look at the rest of the GNUstep stuff. For example you might 
> want to look in some of the themes.
> 
> If you are lucky and don't use "low level" os stuff you might get a working 
> windows version quite easily.
> 
> Riccardo