[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: troubles building 0.6.1

Thanks for the help. It took a while for me to find a shell that comes 
with MacOS X that would work with the build.sh - bash is not included. I 
eventually succeeded with zsh.

My next MacOS X obstacle is figuring out how to open multiple console 
windows. A seemingly trivial obstacle is turning out to be perplexing. 
Once I get ozone running I can't open another window to perform other 
tasks - like running a client app. Probably more appropriate for an OSX 
newsgroup, but if anyone else has encountered this, I would appreciate 
the help.

Other than the issues above, i must say that OSX has been the easiest 
install of a Linux or BSD OS I have ever encountered (small sample set). 
And the GUI doesn't suck either, though it has its oddities.

Jerry

On Sunday, March 25, 2001, at 08:49 AM, Falko Braeutigam wrote:

> On Sun, 25 Mar 2001, Jerry Seeger wrote:
>> I rushed out and bought MacOSX (based on freeBSD) today largelyu so I
>> could experiment with products like Ozone. I have encountered a couple
>> of problems building the app, however.
>>
>> I am putting the project together with ProjectBuilder (If anyone wants
>> it, I will share when I get it working). I have encountered a couple of
>> problems that surprise me as they seem to be with the source files
>> rather than anything I am doing.
>>
>> In TransactionCanvas, I had to add the line 'import
>> org.odmg.Transaction;' to resolve an inability to resolve a symbol.
>>
>> I am getting some other cannot resolve symbol errors. Most of them seem
>> to be associated with the class or interface Env, interface Store, and
>> symbol domLevel2. (The last of those I have not looked into at all.) 
>> For
>> instance, org.ozonedb.core.ClassicStore is supposed to implement Store
>> but there is no sign of that interface anywhere. I checked through all
>> the Sun docs assuming that I just didn't get the latest stuff with this
>> new system, but there is no mention of an interface named Store
>> anywhere. There are a couple of classes named Env here and there, 
>> mostly
>> in example code.
>>
>> So what gives? Why did i have to add an import statement to one of the
>> classes when no one else seems to have to? I look at the code and it
>> really should have the import statement. I'm curious why it works for
>> everyone else.
>
> Probably because they use the Ant build system (build.xml) or the 
> Makefile to
> build ozone ;) Just compiling all *.java files is not enough. Some 
> Castor
> mapping classes have to be generated, OPP has to be compiled before it 
> can be
> used to build proxies, and (and this is your actual problem) there are 
> source
> files included in the package that must not be compiled because they 
> are out of
> synch with the rest of the source tree.
>
>>
>> More important, what do I have to do to get this built? I am very
>> anxious to use Ozone, but as a way to complete a project, not as a
>> project itself.
>
> Just calling build.[sh|bat] should do the job.
>
>
> Falko
> --
> ______________________________________________________________________
> Falko Braeutigam                              mailto:falko@smb-tec.com
> SMB GmbH                                        http://www.smb-tec.com
>