Qt-jambi-interest Archive, June 2007
Qt Jambi final version released
Pages: Prev | 1 | 2 | Next
Message 16 in thread
Hi,
here my experiences with Jambi.
STEP 1: Generate the source code
When I execute ./generator I get:
WARNING(MetaJavaBuilder) :: skipping function 'QHttp::sslErrors', unmatched
parameter type 'QList<QSslError> const&'
Classes in typesystem: 476
Generated:
- java......: 476
- cpp-impl..: 461
- cpp-h.....: 312
- meta-info.: 8
Done, 1 warnings (427 known issues)
How do I avoid the warning?
STEP 2: Build the C++ libraries and tools
Had minor problems with a designer include file. Nothing a sym-link could not fix.
STEP 3: Generate the Ui_Xxx.java files
Seems to be ok. At least no error or warning.
STEP 4: Compile the java source files
javac @java_files results in:
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Is this what I should expect?
The README says:
To run the Examples/Demo launcher, run the:
qtjambi.sh
No qtjambi.sh here. Should it?
The binary package contains a nice qtjambi.jar file. Would be nice if the
source package would generate one, too.
Guido
Message 17 in thread
Guido Seifert wrote:
> STEP 1: Generate the source code
>
> When I execute ./generator I get:
>
> WARNING(MetaJavaBuilder) :: skipping function 'QHttp::sslErrors', unmatched
> parameter type 'QList<QSslError> const&'
Qt Jambi doesn't have ssl support currently. You should be able to add
this fairly easy, by just adding it to the network typesystem definition
if you want to play with it. Otherwise, you can just configure Qt
without ssl support and run the generator again.
Alternativly, ignore the message as it just means some functions will be
missing in the generated API and it shouldn't cause any compile problems.
> STEP 2: Build the C++ libraries and tools
>
> Had minor problems with a designer include file. Nothing a sym-link could not fix.
What was the problem here? ui4_p.h file should be loaded from the
/private subdirectory when building the language plugin.
> STEP 4: Compile the java source files
>
> javac @java_files results in:
>
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
>
> Is this what I should expect?
Yes. javac doesn't like some of our generics code, I'm afraid ;-)
> The README says:
>
> To run the Examples/Demo launcher, run the:
>
> qtjambi.sh
>
> No qtjambi.sh here. Should it?
Since the source package is cross platform it doesn't include .sh, .exe
or .bat, no. The BUILDING_SOURCE_PACKAGE file reffers to the "Manually
launching" part of the README. Here it says which paths you need to
setup, etc.
> The binary package contains a nice qtjambi.jar file. Would be nice if the
> source package would generate one, too.
Just exclude demos/examples/launcher and do:
jar -cf qtjambi.jar com
and you have it.
-
Gunnar
Message 18 in thread
> >STEP 2: Build the C++ libraries and tools
> >
> >Had minor problems with a designer include file. Nothing a sym-link could
> >not fix.
Before I compiled jambi I compiled and installed the newest Qt (4.3.0
open source x11). The folder include/QtDesigner/private was not
included in the installation folder after 'make install'. But as I
said, this was easy to fix.
> What was the problem here? ui4_p.h file should be loaded from the
> /private subdirectory when building the language plugin.
It did, after I linked /private from the source to the intallation
folder.
> Yes. javac doesn't like some of our generics code, I'm afraid ;-)
Great. So except of the minor glitch in STEP 2 everyting worked fine.
> >No qtjambi.sh here. Should it?
>
> Since the source package is cross platform it doesn't include .sh, .exe
> or .bat, no. The BUILDING_SOURCE_PACKAGE file reffers to the "Manually
> launching" part of the README. Here it says which paths you need to
> setup, etc.
Ok, was just wondering whether the build was complete. The previous
warnings made me a bit nervous. Especially since I am not really a JAVA
guy. Not yet, but jambi might change that soon. ;-)
> Just exclude demos/examples/launcher and do:
>
> jar -cf qtjambi.jar com
>
> and you have it.
Thanks. :-)
Guido
