Skip to content
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

[Bug report]: Linux build instructions are inconsistent about the directories used #985

Closed
squeakyneb opened this issue Aug 2, 2024 · 0 comments · Fixed by #986
Closed

Comments

@squeakyneb
Copy link
Contributor

Describe the bug

Following the linux-core-installation simply does not work as-is.

  • The git commands clone to a directory azerothcore though the following sentence says "This will create an azerothcore-wotlk directory containing the AC source files.", which is incorrect.
  • The cmake command sets -DCMAKE_INSTALL_PREFIX=$HOME/azeroth-server/, which is a distinctly different directory again. When you make install, you get the binaries built with entirely invalid references to the surrounding data, and no acore.sh which the rest of the instructions expect to be there.
  • The service units then make reference to ExecStart=/srv/azerothcore-wotlk/acore.sh run-authserver which is yet another directory that doesn't exist. Nothing's been done in /srv at all up to this point in fact (unless it's the user's $HOME, I suppose, but that's unlikely).

Now I don't know the intended correct method, but I worked out was:

  • Clone into $HOME/azerothcore
  • Build with -DCMAKE_INSTALL_PREFIX=$HOME/azerothcore/env/dist/
  • Set the service units to reference /home/[whoever]/azerothcore

Whether to match my method, or something else, the instructions should be adjusted to resolve these issues.

To reproduce

Follow the instructions verbatim. Observe that acore.sh run-authserver can't find the binaries, and (IIRC) the binaries can't start because they've got paths hardcoded to the install directory which is expected to include other content that isn't present.

Expected behavior

Following the instructions verbatim should produce a working application.

Screenshots

No response

Desktop

N/A (this was a build on Rocky Linux 8 but there is no system in the world where this would work any differently)

Smartphone

N/A

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant