New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support resource access from modules without loading them #15

Closed
saschazelzer opened this Issue Mar 8, 2014 · 3 comments

Comments

Projects
None yet
1 participant
@saschazelzer
Member

saschazelzer commented Mar 8, 2014

This would be a nice feature but still needs to be investigated, especially in a cross-platform set-up.

@saschazelzer saschazelzer added this to the Releasse 3.0 milestone Mar 8, 2014

@saschazelzer saschazelzer added the feature label Mar 8, 2014

@saschazelzer saschazelzer self-assigned this Mar 8, 2014

@saschazelzer

This comment has been minimized.

Show comment
Hide comment
@saschazelzer

saschazelzer Sep 4, 2014

Member

The branch development...15-resources-without-loading-modules now implements a resources system which uses zip archives appended to shared libraries. Static modules do not work yet.

Member

saschazelzer commented Sep 4, 2014

The branch development...15-resources-without-loading-modules now implements a resources system which uses zip archives appended to shared libraries. Static modules do not work yet.

@saschazelzer

This comment has been minimized.

Show comment
Hide comment
@saschazelzer

saschazelzer Sep 8, 2014

Member

The latest commit 1ac36fe (merged already into development) now contains support for static modules as well.

To benefit from being able to access resources from modules without loading them, a new module state needs to be introduced, which models the INSTALLED state (and possibly RESOLVED).

Member

saschazelzer commented Sep 8, 2014

The latest commit 1ac36fe (merged already into development) now contains support for static modules as well.

To benefit from being able to access resources from modules without loading them, a new module state needs to be introduced, which models the INSTALLED state (and possibly RESOLVED).

@saschazelzer

This comment has been minimized.

Show comment
Hide comment
@saschazelzer

saschazelzer Oct 30, 2014

Member

Issues with codesign and otool on MacOS have been resolved by linking the resource files into the module instead of appending it at the end. This link mode is also available on Unix (with gcc -b binary) and Windows (using rc files). Link mode is currently used by default only on MacOS.

Member

saschazelzer commented Oct 30, 2014

Issues with codesign and otool on MacOS have been resolved by linking the resource files into the module instead of appending it at the end. This link mode is also available on Unix (with gcc -b binary) and Windows (using rc files). Link mode is currently used by default only on MacOS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment