Allow build with systems libenet#159
Allow build with systems libenet#159susnux wants to merge 1 commit intoassaultcube:masterfrom susnux:system_enet
Conversation
|
Unless those distributions plan to synchronize future updates of their enet packages with the release dates of AC, this is a horrible idea. |
|
Of cause, but normally if the protocol changes also the version of enet changes so the .so number will change. |
|
Why on earth should we open that can of worms just to eliminate 50k of static library? (Also, 1.2.0.2 already fails on some platforms, because it requires an old version of libcurl.) Just think of it as a code part of AC that looks very much like a commonly known network libarary. Btw: recent development versions are no longer compatible to stock enet anyway :) |
|
Ok. |
|
a) "it's working now" is irrelevant, as long as you can't guarantee the system enet library to stay compatible There is absolutely nothing to gain for us by using the system lib for enet. |
|
Ok |
Make it possible to build with system libenet, so packaging is easier.
This is already done by Arch Linux or openSUSE.