summaryrefslogtreecommitdiff
path: root/shell/Library_ooofilt_x64.mk
AgeCommit message (Collapse)AuthorFilesLines
2012-11-15Bin use of UTF-16 expat variant in the Windows shell extensionTor Lillqvist1-1/+1
Thus we can drop that variant completely. Change-Id: I11a8e40436921219bd6dd4afad4c7907ccb6b84c
2012-10-27shell: use x64 zlib version hereMatúš Kukan1-1/+1
Change-Id: Ie61966f28b937db7d4997753cc388332dda25f63
2012-10-25gbuildification of expatDavid Ostrovsky1-1/+1
Two different xmlparse libraries are created: ascii_expat_xmlparse and expat_xmlparse. One without -DXML_UNICODE and one with. Source file are duplicated and renamed with gb_UnpackedTarball_set_post_action function to be able to add artifacts twice to gbuild machinery. On windows 64 bit additional two librares are created: expat_xmlparse_x64 and expat_xmltok_x64. That is due the problem with shell/shlxthandler (comment): ------------------------------------------------------ use UNICODE only because shell/shlxthandler doesn't link against ascii_expat_xmlparse ------------------------------------------------------ Include files are delivered to $(OUTDIR)/inc/external/expat now and not to $(OUTDIR)/inc/external any more. set_include call is added in RepositoryExternal.mk. To define dependency between StaticLibrary and ExternalProject new function was introduced: gb_StaticLibrary_use_external_project. Change-Id: I3b3aa40f39ef82c70f6f28790b582c83e48bdf76
2012-10-05shell: no need to define XML_UNICODE ...Michael Stahl1-1/+0
... because it is added automatically by the external expat_utf16. Change-Id: Ifdad11b275f7074be6f2e92df2e3c30c7097a5b7
2012-09-28gbuild: gb_Library_PLAINLIBS_NONE cleanup for WNT:Michael Stahl1-2/+2
add a new gb_LinkTarget_use_system_win32_libs to abstract different linker options on MSVC and GCC. Change-Id: Ic9bf2545f59bf7871e6fc06b290c486ddfbec03d
2012-05-30do not link with cmt by defaultDavid Tardon1-0/+1
It causes linker errors like: libcmt.lib(crt0dat.obj) : error LNK2005: _amsg_exit already defined in +msvcrt.lib(MSVCR90.dll) ... Change-Id: I54217859a7c4f6535eed5bca50ada68a8d5b095c
2012-05-30use 64-bit compiler and linker for 64-bit Windows shell extensionsAndras Timar1-1/+1
Change-Id: I4ad94eca4ebbf7d8e989dba5a19296d727111850
2012-05-29copy the source files before trying to use themDavid Tardon1-0/+4
Change-Id: I3252511cd845e6f91d31f5b5858c9122fcab4838
2012-05-29trying to fix shell x64 build on WindowsAndras Timar1-1/+1
Change-Id: Ibf5dffec5f5617d225f6f529566b524ebafc20c2
2012-05-29partially revert 3ca7b8c296bcda699bcf642db3932b3fdbe7ad06Matúš Kukan1-4/+4
It is not possible to use PRIVATE this way. So, there are still warnings as: LINK : warning LNK4104: export of symbol 'DllCanUnloadNow' should be PRIVATE Change-Id: I9f14dd95b611475ef89914270c931a7115f1f5c8
2012-05-29shell: export more symbols, as privateMatúš Kukan1-6/+4
Change-Id: Ifca9712c2ee28c8e38925150b3e6d0f27195ff1d
2012-05-29export COM functionsDavid Tardon1-0/+9
Change-Id: I5ab936c90b596716f92f04d0db46a77a656a758b
2012-05-29gbuildize shellDavid Tardon1-0/+85
Change-Id: I91a89f9d0bd1eb88a94179f1c1a41bc832599fed
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-14 10:03:24 +0000