summaryrefslogtreecommitdiff
path: root/scripting/Jar_MemoryUsage.mk
AgeCommit message (Collapse)AuthorFilesLines
2014-04-28prefer makefile-gmake-modeTakeshi Abe1-1/+1
Change-Id: I9cc9bfbddd3a90e00eee3e674994e5d6207f9034
2013-04-30Move to MPLv2 license headers, with ESC decision and author's permission.Michael Meeks1-23/+4
2012-08-17gbuild: register all jarsMichael Stahl1-4/+4
Change-Id: I9f49970e5e06d1afd3fc066a20d1671c93e262fc
2012-04-08gbuild: "use" vs. "add":Michael Stahl1-1/+1
Naming convention for gbuild methods: - "add" is used for stuff that is logically a part of the target (i.e. not registered at the Module, but defined in the target's makefile) - "use" is used for stuff that is logically a different target (i.e. it is registered at the Module, has it's own makefile, may be in a different module than the target)
2012-03-23fdo#46102: Fix Java script examples after gbuild'ificationStephan Bergmann1-0/+2
...they contained no class files anymore, due to missing gb_Jar_set_packageroot calls. However, those calls only work for subdirectories, i.e., the example .java files need to be put into a package (I chose org.libreoffice.example.java_scripts) for all of them). This in turn required adaption of the parcel-descriptor.xml files; not sure what the logicalname entries there are good for if anything -- the macro names at "Tools - Macros - Run Macro..." now unfortunately(?) contain the fully qualified paths for the HelloWorld, HighlightText, and MemoryUpdate examples. There are additional examples at scripting/examples/java/ that apparently do not get packaged (but I adapted them anyway).
2011-10-23no need for SRCDIR parameter hereMatúš Kukan1-1/+1
2011-10-01finished converting scripting to gbuildMatúš Kukan1-0/+42