[Mono-bugs] [Bug 662228] Provide a way to leave assets uncompressed

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=662228

https://bugzilla.novell.com/show_bug.cgi?id=662228#c3


--- Comment #3 from Jonathan Pryor <jpryor at novell.com> 2011-01-16 03:11:04 UTC ---
r9136 takes an initial stab at this.

The solution used here adds the '-0 EXT' option to monodroid.exe 
(which forwards the same value to `aapt`), and also accepts an optional
//AssetManager/StoreUncompressed boolean element into the .csproj; to
specify that a file should be stored uncompressed:

    <AndroidAsset Include="Assets\Hello.bin">
      <StoreUncompressed>True</StoreUncompressed>
    </AndroidAsset>

Our MSBuild support will then grab the file extensions and turn this
into `monodroid -0 EXT` values (which are then provided to `aapt`).

PRO: It works (reasonably).  (Or you can just use '-0 EXT' in
<MonoDroidExtraArgs/>.)

CON: File storage/non-compression is handled by file extensions; the
above mechanism doesn't actually convey that, and implies it's a
per-file decision (when it isn't).  For example:

    <AndroidAsset Include="Assets\Hello1.txt">
      <StoreUncompressed>True</StoreUncompressed>
    </AndroidAsset>
    <AndroidAsset Include="Assets\Hello2.txt">
      <StoreUncompressed>False</StoreUncompressed>
    </AndroidAsset>

would result in both Hello1.txt and Hell2.txt being stored w/o
compression, despite the <StoreUncompressed>False</StoreUncompressed>.

This might not be that bad of a con; we could always manually add the
files w/o compression as we do for assemblies, so I'm not sure that
this is enough to nix the idea.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.