mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
9917a51ee8
Indicating a jar currently looks like the following in a jar manifest: path/to/name.jar: The `path/to` doesn't contain the implicit "chrome/" directory. This, in turn, doesn't allow much flexibility to use the jar maker for what is not necessarily under chrome/. To use the jar maker to fill some chrome manifest for the default theme extension, we currently use a hackish path to get to the right location, and rely on the chrome.manifest file in the parent directory never to be picked by the package manifest, which is a quite horrible way to do this, but worked well enough for that specific use case. With the need to handle system addons at the build system level, it becomes necessary to come up with something less hackish. What this change introduces is an additional syntax for the jar manifest, in the following form: [base/path] sub/path/to/name.jar: Using this syntax, there is no implicit 'chrome' path. The `base/path` is relative to the current DIST_SUBDIR, and the `sub/path` is relative to that `base/path`. The distinction can be useful for build system backends. The assumption that the "root" chrome.manifest is in the parent directory of the implicit "chrome" directory dies, and the `base/path` is where the root chrome.manifest is placed. |
||
|---|---|---|
| .. | ||
| mozbuild | ||
| androideclipse.rst | ||
| build-overview.rst | ||
| build-targets.rst | ||
| cppeclipse.rst | ||
| defining-binaries.rst | ||
| environment-variables.rst | ||
| files-metadata.rst | ||
| glossary.rst | ||
| index.rst | ||
| jar-manifests.rst | ||
| mozbuild-files.rst | ||
| mozbuild-symbols.rst | ||
| mozconfigs.rst | ||
| mozinfo.rst | ||
| pgo.rst | ||
| preprocessor.rst | ||
| python.rst | ||
| slow.rst | ||
| supported-configurations.rst | ||
| test_manifests.rst | ||
| visualstudio.rst | ||