R20 installs files to incorrect locations...

This is due to the install step of the new build system, it is not yet complete :)

Why are we changing build systems AGAIN? This is why we keep having issues. I am unable to even start the binaries for debugging.

Because the old one is horribly broken and is just a patch job for this to work as is. Also, this is an attempt at fixing the cmake build to be cross platform. Not a change. All of the above is simply install step settings.

What was broken in the old system? It worked fine on several platforms for me. This, from my perspective, looks like it is being made to be more like a Windows application.

Alright, Foereaper explained changes which do not appear to be documented on our forum to me. The addition of the new cmake parameter will clear PART of this up. We now need a parameter for where to place binaries. I will suggest that when these parameters are omitted, we default to the correct locations. Under Unix/Linux/BSD/Apple/Solaris/etc this will be "etc" for configuration files and "bin" for the binaries. Under Windows I would suggest "%Userdocs%/My Games/MaNGOS" for the configuration files and wherever the user wants for the binaries. This way when these parameters are omitted we still get a sane solution on all systems.

As of this commit: [URL]https://github.com/mangoszero/server/commit/7e30aa81d033ea89b07cfd307b3310c943488a54[/URL]

Linux:
- Binary files are now installed at install_prefix/bin
- Config files are now by default installed to install_prefix/etc

Windows:
- Binary files are now installed at install_prefix
- Config files are now by default installed to install_prefix

CONF_DIR option is relative to install_prefix on both Windows and Linux. On linux this option defaults to: -DCONF_DIR=etc/

Notes:

lua_scripts directory and log files location are relative to the binary directory, this means;
Linux: install_prefix/bin
Windows: install_prefix

This can be changed in mangosd.conf, ie.

LogsDir = "../logs/"

The above would set the logs directory to:

install_prefix/logs

I will update my end and check it out. Questions abound however. You stated that "CONF_DIR" is relative to the install prefix. Does this mean that I cannot set my prefix to "/home/wow/zero" and my configuration directory to something like "/etc". I would not do such a thing, but I want to know. On my production server I install to "/usr". This places my stuff in a spot where any user can fire up their own server. My end goal is to have a Debian/Ubuntu package users can install. However, configuration files do go to "/etc". Is this possible? If not it is no big deal, but it would be nice to follow the normal method for configurations. My backup plan would be to create a symlink to "/etc" in "/usr" during the install so the configuration files are in the correct spot.

Say your install prefix is /home/usr/server. By default, the config dir would then be /home/usr/server/etc. If you would like the config dir to be /home/usr/etc, you would then use -DCONF_DIR=../etc/

[quote=Foereaper]Say your install prefix is /home/usr/server. By default, the config dir would then be /home/usr/server/etc. If you would like the config dir to be /home/usr/etc, you would then use -DCONF_DIR=../etc/[/quote]
Is it possible to set "CONF_DIR" to "/etc"? If so I can begin making the Debian packages again.

[quote=Xenithar]Is it possible to set "CONF_DIR" to "/etc"? If so I can begin making the Debian packages again.[/quote]

Yes, however I will have to look into the technical aspects of doing this, as it may cause some issues with relative pathing. Will get to it once I have some spare time.

No problem. I can work around it for now. Let me know when I can set the configuration path exclusively.

Has this been resolved ?

I believe so. I will find out when I build the new server tomorrow. I can then salvage my data off the old drive and see how I was configuring the servers. I automated most of the build with scripts.