On 16 February 2012 00:52, Matúš Kukan matus.ku...@gmail.com wrote:
I had a look but couldn't build jurt:
So, if we don't want to use $(OUTDIR)/class, adding
+$(eval $(call gb_Jar_add_jars,jurt,\
+$(WORKDIR)/CustomTarget/ridljar/javamaker/class \
+))
in Jar_jurt.mk seems to help. I wonder
On Thu, Feb 16, 2012 at 11:38:07AM +0100, Matúš Kukan wrote:
On 16 February 2012 00:52, Matúš Kukan matus.ku...@gmail.com wrote:
I had a look but couldn't build jurt:
So, if we don't want to use $(OUTDIR)/class, adding
+$(eval $(call gb_Jar_add_jars,jurt,\
+
On 16 February 2012 13:29, David Tardon dtar...@redhat.com wrote:
The generated UNO classes must be present in ridl.jar . They are (or
should be) added into the jar by
$(eval $(call gb_Jar_add_packagedirs,ridl,\
$(WORKDIR)/CustomTarget/ridljar/javamaker/class/com \
))
Ok, so they were
On 16 February 2012 15:29, Matúš Kukan matus.ku...@gmail.com wrote:
- $(foreach root,$(PACKAGEDIRS), $(gb_Jar_JARCOMMAND) uf $(2)
-C $(dir $(root)) $(notdir $(root))) \
+ $(foreach root,$(PACKAGEDIRS), cd $(dir $(root))
$(gb_Jar_JARCOMMAND) uf $(2) $(notdir $(root))) \
helps
On Thu, Feb 16, 2012 at 03:29:59PM +0100, Matúš Kukan wrote:
On 16 February 2012 13:29, David Tardon dtar...@redhat.com wrote:
The generated UNO classes must be present in ridl.jar . They are (or
should be) added into the jar by
$(eval $(call gb_Jar_add_packagedirs,ridl,\
On 14 February 2012 06:55, David Tardon dtar...@redhat.com wrote:
On Mon, Dec 26, 2011 at 01:33:57PM +0100, David Tardon wrote:
I have converted 6 modules to gbuild on branch feature/gbuild_java:
javaunohelper, jurt, jvmaccess, jvmfwk, ridljar and unoil. It builds
fine here and smoketest
On Mon, Dec 26, 2011 at 01:33:57PM +0100, David Tardon wrote:
Hi all,
I have converted 6 modules to gbuild on branch feature/gbuild_java:
javaunohelper, jurt, jvmaccess, jvmfwk, ridljar and unoil. It builds
fine here and smoketest finishes with status OK, but some of the modules
contain
I actually waited a lot longer than promised and there is still no
response from any developer using Windows.
You misunderstand how this works. It's the Windows-based developers
who have to make sure they don't break the Linux build, not the other
way around.
--tml
