Fix-gitignore-autogenpath - #1150
Conversation
Fixes the path to be the proper path for gitignore. From #1149.
|
Why? The other path doesn't lead into anything? |
|
In your machine it doesn't but on Linux the app is named AttorneyOnline without the underscore. |
|
Oh, I see. Alright. |
|
So, why does it do that? Why is it not consistent? I mean, there's an underscore after AttorneyOnline_autogen regardless. |
|
the build target is consistently named AttorneyOnline now. only for final distribution are spaces added (Attorney Online.exe, Attorney Online.bin etc) if you do ./configure clean, ./configure and build it should autogen into the AttorneyOnline_autogen folder correctly |
|
I see. Thank you. This feels like something that should have been noted before any of these changes were put in, both by the maintainer approving and the contributor, but whatever. AttorneyOnline_autogen it is. That said, what else has been changed? I noticed there's a libqapng.dylib check now, for example? |
|
You're right, the build target renaming should have been displayed better in the PR. .dylib is the format of dynamic libraries for macOS. it ensures that apng files can be rendered correctly there. Additionally, the zip files generated from github now has more explicit names, ie. eg. |
|
Right. I understand that part, I'm more so talking about the changes incurred to the windows qtapng. Are you able to confirm that it properly takes the qtapng.dll from the image formats inside a same-directory qtapng clone? And, I see, that's an acceptable change, thank you. This is somewhat hijacking of this PR to address a prior PR, which isn't that good, so I apologize for that. I think that can continue for now regardless. |
|
Yes, I tested it on Windows and the app is configured to complain very loudly if apng support is missing. (info box) You can check this by downloading the latest Windows artifact built from master: https://github.com/AttorneyOnline/AO2-Client/actions/runs/32830280648 |
|
Nice. Alright. And yeah, showing the base folder isn't a bad idea, especially with mounted folders being a possibility, though it does show there. Either way, there is no harm in it. Could I ask you to provide the source of your qtapng (windows)? I assume you're building it with MinGW, or llvm-mingw. |
|
It's all handled in configure.sh, on line 332: Line 332 in 96d9f3e It simply pulls the source code from another git repo (https://github.com/jurplel/QtApng.git) and compiles it per platform. The whole bash function looks like this: |
|
I'm trying it continuously at the moment, it works on MSVC just fine, but on mingw/llvm-mingw it does not recognize it at all. Are you sure you've tried this on both debug/release, on windows, via QT6 (or qt 6.10/6.11) (on any creator version above 19)? |
|
Can you elaborate on "does not recognize it" means? Do you have the full output of your |
|
May I ask what the difference is between QT_ROOT and QT_ROOT_DIR? |
|
QT_ROOT is QT_ROOT is only used internally while QT_ROOT_DIR is what's passed to configure.sh (matching CI behavior) |
|
So a couple of things; Qt Maintenance Tool's default install path is Effectively it's as it says in configure.sh help section; either you define QT_ROOT_DIR explicitly or we'll make a guess to where Qt is. Regarding apng, Your configure.sh output seems truncated and there's no useful information there other than it cloned correctly. Is QtImageformats in the Qt installation? I'm not very preoccupied on the particular naming. If you think passing QT_PATH is easier we can do that too. |
|
Handled, thank you. And the name is fine. |


Fixes the path to be the proper path for gitignore. From #1149.