Hi Andrew,
I'd like to do that. Anyone there willing to help me reviewing the article when it's ready? :-)
[]s, Fernando Lozano
It'd be nice if we could make an updated article similar to this one:
http://www-128.ibm.com/developerworks/library/j-nativegui/
Andrew
Hi Fernando,
* fernando@lozano.eti.br fernando@lozano.eti.br [2006-06-08 14:28]:
I'd like to do that. Anyone there willing to help me reviewing the article when it's ready? :-)
I will help review it.
Thanks!
Andrew
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
fernando@lozano.eti.br wrote:
Hi Andrew,
I'd like to do that. Anyone there willing to help me reviewing the article when it's ready? :-)
[]s, Fernando Lozano
The article is somewhat pointless in its current form, since where it says get and build X, you can just say to install the X-devel RPM.
The more import issue is whether aot-compile-rpm can be used outside of RPM now since the preferred way seems to be to build applications is not by linking an exe, but my using aot-compiled jars. Is this so?
- -- Sincerely,
David Walluck david@zarb.org
* David Walluck david@zarb.org [2006-06-08 15:09]:
The more import issue is whether aot-compile-rpm can be used outside of RPM now since the preferred way seems to be to build applications is not by linking an exe, but my using aot-compiled jars. Is this so?
I believe Gary had worked on making it aot-compile and aot-compile-rpm just a wrapper that does the RPM-specific stuff. AFAIK work was underway on aot-compile-deb as well but I could be way off base there.
Gary?
Andrew
Andrew Overholt wrote:
- David Walluck david@zarb.org [2006-06-08 15:09]:
The more import issue is whether aot-compile-rpm can be used outside of RPM now since the preferred way seems to be to build applications is not by linking an exe, but my using aot-compiled jars. Is this so?
I believe Gary had worked on making it aot-compile and aot-compile-rpm just a wrapper that does the RPM-specific stuff. AFAIK work was underway on aot-compile-deb as well but I could be way off base there.
Gary?
Very recent java-gcj-compat (1.0.56 or higher) has two scripts, the original aot-compile-rpm and a new aot-compile which takes command line options and can be used manually or (presumably) within dpkg builds. It's not in FC5, though, which has 1.0.52.
Cheers, Gary
On Fri, 2006-06-09 at 09:05 +0100, Gary Benson wrote:
Very recent java-gcj-compat (1.0.56 or higher) has two scripts, the original aot-compile-rpm and a new aot-compile which takes command line options and can be used manually or (presumably) within dpkg builds. It's not in FC5, though, which has 1.0.52.
Should we start using aot-compile in our spec files instead of aot-compile-rpm?
Ben
Ben Konrath wrote:
On Fri, 2006-06-09 at 09:05 +0100, Gary Benson wrote:
Very recent java-gcj-compat (1.0.56 or higher) has two scripts, the original aot-compile-rpm and a new aot-compile which takes command line options and can be used manually or (presumably) within dpkg builds. It's not in FC5, though, which has 1.0.52.
Should we start using aot-compile in our spec files instead of aot-compile-rpm?
aot-compile exists for non-rpm builds and for debugging purposes. aot-compile-rpm remains the recommended way to native compile rpms.
Cheers, Gary
On Thu, 2006-06-08 at 16:28 -0200, fernando@lozano.eti.br wrote:
I'd like to do that. Anyone there willing to help me reviewing the article when it's ready? :-)
I would love to read it. It should probably just point out which packages to install to have a developers setup and the appropriate libraries (instead of trying to explain how to build everything from scratch). And then have a bit more explanations and examples how to actually build your own application using those standard packages.
Cheers,
Mark
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Mark Wielaard wrote:
scratch). And then have a bit more explanations and examples how to actually build your own application using those standard packages.
Right, so if aot-compile-rpm is the ``right'' way to build Java applications, it should not be limited to rpm.
Moreover, ``everyone'' knows that the right way to install even your own applications is through a package manager, and it would actually be pretty easy to provide a rpm .spec template for Java packages, but then, getting into RPM packaging would be the subject of a whole other article.
Still, best practices of actually installing SWT from RPM rather than compiling it yourself and throwing it into /usr/local are more obvious suggestions that can actually be used.
- -- Sincerely,
David Walluck david@zarb.org
java-devel@lists.fedoraproject.org
-
Andrew Overholt -
Benjamin Konrath -
David Walluck -
Fernando Lozano -
Gary Benson -
Mark Wielaard