Re: [jnc-users] JNC hangs

[Marco T. <mt...@gm...>]

Lee D. Painter wrote:
>>> Yesterday something else started happening, it started to compile
>>> without getting stuck when using it through the JNC 1.1 GUI but the
> link
>>> fails with multiple definition errors again (see below). This seems
> to
>>> have no pattern as sometimes it compiles and others it gets stuck as
> per
>>> the original problem. I did change some virtual memory settings
> before
>>> this happened though but when monitoring the compile everything
> seems to
>>> be within limits.
>> Hmmm... If it works now, I'd suggest we blame the memory (swap) and go
>> on with life... After all, I never had problems compiling SWT.
> 
> I'm hoping this is limited to the one workstation and I'll do some
> testing on our actual automated build machines.

Compiled jars are cached (unless you removed that flag). So just ensure 
that the compilation runs through the first time.


>> Since 1.1, the package java.text is also excluded if you check the
>> "exclude gui" box. Your code depends on it... Either change the code
> or
>> uncheck the "exclude gui" box.
>> There's a faq entry on the homepage about these "multiple definition"
>> errors if you're interested...
> 
> Right that makes sense as to why it fails but I was unaware that
> java.text was excluded in 1.1 and not 1.0.1

It's listed in the GUI at the "Exclude GUI" option.


> and there is no indication
> of that in the FAQ.

No, but a description of why "multiple definition" errors occur and that 
it is because of "Exclude GUI" or "Exclude JCE".


> Should that be considered as part of the GUI? It has
> date formats and i18n stuff which can be used outside of Swing and AWT.

Actually you're right. But I added it because I had to take it from a 
Sun JRE because the GNU Classpath one is broken. So, if you exclude the 
GUI, you're sure that you do not have to follow the Sun license.


> I've now turned off the excluded GUI flag but now I have a 6MB exe with
> 1.1 instead of 2.3 MB with 1.0.1. So this really does not help in my
> case as 6MB is not an acceptable size given that it is includes
> AWT/Swing when we don't even use it.

See, size matters ;-)
Well, just find the part that uses java.text and remove/recode it.


> Download size is quite important
> for this application and is one of the reasons we spent the time
> converting to SWT in the first place :(

Shouldn't be too complicated to get that working...


Marco