summaryrefslogtreecommitdiff
path: root/extensions/Library_OOoSpotlightImporter.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
2013-01-26gbuild: fix silly "expandtabs" in makefile VIM modelinesMichael Stahl1-1/+1
Change-Id: I54d8923ad315e8041fd3904da3a29f1a7a8c8b16
2012-09-28gbuild: clean up Mac OS X framework handling:Michael Stahl1-4/+4
There are currently 3 different mechanisms being used for frameworks, which is of course intolerable so we invent a 4th one and standardize on it: gb_LinkTarget_use_darwin_frameworks (This doesn't mean using add_libs or externals was wrong, it was just inconsistent... and i don't see an obvious benefit of using externals here) Change-Id: I5de9020402c87e7236c6a358c47f02fa56642d3d
2012-03-23Move spotlight plugin out of minizipFridrich Štrba1-2/+0
2012-01-04gbuild: macosx.mk: add gb_Library_BundleMichael Stahl1-3/+1
...and use it to build OOoSpotlightImporter. This isn't particularly elegant, but then again, why the heck does dyld have different dynamic library types in the first place?
2012-01-04Hack to get OOoSpotlightImporter building: FIXME this is prolly not correctNorbert Thiebaud1-1/+2
2011-12-19extensions: d'oh, i've pasted C++ emacs modelines in makefilesMichael Stahl1-1/+1
2011-12-17extensions: convert spotlight to gbuildPeter Foley1-0/+52