-
Notifications
You must be signed in to change notification settings - Fork 93
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
Odd path calculation with --hl2sdk-manifests with sample plugin #154
Comments
Also having some odd issues with this. If I try to use absolute paths, e.g. -
I end up with
which seems to be caused by some path computation down inside of AMBuild. If I try to use a relative path, e.g. -
I end up with
which I assume is because the relative path ends up being relative to configure.py, however if I try to adjust for that, e.g. -
it gets further, but I end up with
where the path is seemingly relative to the build directory for this path computation (not configure.py). |
More closely read - and I realized the hl2sdk-manifests module needs to be accessible from the directory containing configure.py, and the path you're passing the command line needs to be relative to that seemingly. |
Has anybody found a solution to this? I am trying to compile cd metamod-source/samples/s2_sample_mm
mkdir build
cd build
python ../configure.py -s insurgency --mms_path /mnt/hdd/alliedmodders/metamod-source/ --hl2sdk-root /mnt/hdd/alliedmodders/ --hl2sdk-manifests /mnt/hdd/alliedmodders/metamod-source/hl2sdk-manifests/ This fails with this output: I tried using a relative path for Almost there! So I tried this: This is really frustrating. After 2 weeks of messing around late 2023, I finally managed to compile a basic "Hello World" MM:S plugin, but now I can't remember how I did it. I believe I was using somebody's personal MM:S template repo. I'll have to see if I can find the upstream URL for it... |
I found it, here is the template repo I used before: I was able to compile it like this: git clone https://github.com/nosoop/mmsplugin-base
mkdir mmsplugin-base/build
cd mmsplugin-base/build
python ../configure.py -s insurgency --hl2sdk-root /mnt/hdd/alliedmodders --mms_path /mnt/hdd/alliedmodders/metamod-source This gives an error:
To fix this, I just commented out line 168 of python ../configure.py -s insurgency --hl2sdk-root /mnt/hdd/alliedmodders --mms_path /mnt/hdd/alliedmodders/metamod-source
ambuild I don't know if this info will help anyone, but I hope it might! |
This has now been addressed with the below. The hl2sdk-manifests directory should be able to live anywhere now, as long as a valid path is given, and relative paths are now better supported for that directory, as well as MM:S's and the SDK root. |
Given the folder structure below, running the following command inside the build folder will result in the script trying to find
hl2sdk-manifests
inplugin/hl2sdk-manifests
instead.python3 ../configure.py --hl2sdk-root <hl2sdk root> --mms_path "../metamod-source" --hl2sdk-manifest "../hl2sdk-manifests" -s cs2 --targets x86_64
The text was updated successfully, but these errors were encountered: