-
Notifications
You must be signed in to change notification settings - Fork 595
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
New assets system #1904
Comments
Im not sure we had a sufficient amount of consensus on the issue of how to handle extracted textures specifically-- I recall only 3 people voicing support for the "extract both inc and png but only use inc" idea. But this can possibly be discussed again and have a stronger agreement when it comes time to actually make this change. |
Summary of the textures (as png) topicCurrent mainIn current main, as an example the directory layout limited to handling a single texture looks like:
Chronologically, what happens is On On When a png is modified, the corresponding .inc.c is rebuilt accordingly
FutureIn the currently proposed future system, as an example the directory layout limited to handling a single texture looks like:
Chronologically, what happens is On
On In this scheme, For example this allows the following workflow to change a vanilla texture:
Discussion on "Future" choicesWhy not generate the .inc.c from
|
#1967 extracts like Both use It would be fine to change new assets to also use Then |
re: #1904 (comment) I think it would be wise to just not have two files named the same ( |
#1973 (review) : to be changed by new assets : don't reference gkeep globally, unduplicate xmls |
Just need a home for the directory layout we agreed upon, so I can find it again
Productive discussion on discord happened
from https://discord.com/channels/688807550715560050/688851317593997489/1207388581639880745
to https://discord.com/channels/688807550715560050/688851317593997489/1208159004694413312
The general result is a new top level folder
extracted/
for extracted things, including assets, text and baserom segmentsI compiled the changes to "future layout", see below
in the following directory structure layouts:
[first/part/]second/part
paths are where the file does#include "second/part"
, and CPP resolves it tofirst/part/second/part
(due tofirst/part
being in the include path)future layout
"future layout v4":
Include path would be like
-Ibuild/VERSION -Iextracted/VERSION
history:
v3->v4: removed extracted/VERSION/text/message_data.enc.h (no clue why it was there)
v2->v3: fix oversimplified text handling. cf #1730 (comment)
v1->v2: cf discord discussion linked above
v1:
assets/_extracted/
, cf #1730 (comment)current zeldaret/main layout
For reference.
"current zeldaret/main layout v4" (since 9def6f4):
-Ibuild/VERSION -Iextracted/VERSION
History:
v3 (since bf37ad1 and before 9def6f4):
-Ibuild/gc-eu-mq-dbg -Iextracted/gc-eu-mq-dbg
v2: since a6f646d and before bf37ad1
(didn't write it out, in-between v1 and v3: has text in extracted/ but not baserom files)
v1 (before a6f646d):
-Ibuild/gc-eu-mq-dbg
The text was updated successfully, but these errors were encountered: