Command line tool to edit resources of exe
Перейти к файлу
dependabot[bot] e36b688b42
chore: bump actions/checkout from 4.2.0 to 4.2.2 (#147)
Bumps [actions/checkout](https://github.com/actions/checkout) from 4.2.0 to 4.2.2.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](d632683dd7...11bd71901b)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-10-31 23:48:47 -07:00
.github chore: bump actions/checkout from 4.2.0 to 4.2.2 (#147) 2024-10-31 23:48:47 -07:00
src chore: restore help version format (#121) 2023-11-15 17:36:47 -08:00
.editorconfig Add .editorconfig with two-space indents and Unix newlines 2016-01-29 00:36:37 -08:00
.gitignore feat!: build with CMake and release with semantic-release (#118) 2023-11-15 14:03:14 -08:00
.releaserc.json chore: migrate default branch to main (#122) 2023-11-15 18:31:07 -08:00
CMakeLists.txt feat!: build with CMake and release with semantic-release (#118) 2023-11-15 14:03:14 -08:00
LICENSE Initial commit. 2013-11-05 19:31:48 +08:00
README.md feat!: build with CMake and release with semantic-release (#118) 2023-11-15 14:03:14 -08:00

README.md

rcedit

Continuous Integration

Command line tool to edit resources of exe file on Windows.

Executables

Prebuilt binaries can be found in the GitHub releases.

Building

To build you need CMake 3.15+ and Visual Studio 2015 or above.

  1. Clone the repository
  2. Create a build directory: cmake -E make_directory build
  3. Change to the build directory: cd build
  4. Make the CMake project: cmake ..
  5. Build: cmake --build .

Docs

Show help:

$ rcedit -h

Set version string:

$ rcedit "path-to-exe-or-dll" --set-version-string "Comments" "This is an exe"

Use this option to change any supported properties, as described in the MSDN documentation here

Set file version:

$ rcedit "path-to-exe-or-dll" --set-file-version "10.7"

Set product version:

$ rcedit "path-to-exe-or-dll" --set-product-version "10.7"

Set icon:

$ rcedit "path-to-exe-or-dll" --set-icon "path-to-ico"

Set resource string:

$ rcedit "path-to-exe-or-dll" --set-resource-string id_number "new string value"

Set requested execution level (asInvoker | highestAvailable | requireAdministrator) in the manifest:

$ rcedit "path-to-exe-or-dll" --set-requested-execution-level "requireAdministrator"

Set application manifest:

$ rcedit "path-to-exe-or-dll" --application-manifest ./path/to/manifest/file

And you can change multiple things in one command:

$ rcedit "path-to-exe-or-dll" --set-icon "path-to-ico" --set-file-version "10.7"

Get version string:

$ rcedit "path-to-exe-or-dll" --get-version-string "property"

Use the same properties as --set-version-string. Use "FileVersion" to get the results of --set-file-version and "ProductVersion" to get the results of --get-product-version.

Get resource string:

$ rcedit "path-to-exe-or-dll" --get-resource-string id_number