Fork me on GitHub
Drop Visual Studio solution/project files and require cmake (boost lib path issue)
Post: #11
No. It's a broader problem. Another possibility that might allow us to avoid the problem for now would be to use ASIO in header-only mode. Then we wouldn't need the .lib files. I have been exploring this possibility.

Edit: Update -- boost ASIO cannot be compiled header-only. It always requires the binary for boost::system, as noted here: http://think-async.com/Asio/AsioAndBoostAsio
Reply
Post: #12
cmake can be configured so that it puts the binaries into specific folders, a long time ago i even opened an issue for it but never took care of it: https://github.com/cmangos/issues/issues/88

i'm still all in favour of dropping the VS files (we started that discussion in 2013, maybe even earlier: https://github.com/cmangos/issues/issues/69 Wink)
Reply
Post: #13
I am referring to the boost binary folder, not the cmangos binary folder.
Reply
Post: #14
(03-02-2016, 08:39 PM)namreeb Wrote: I am referring to the boost binary folder, not the cmangos binary folder.

sorry for not having been clear, my reply was to Xfurry:
(02-29-2016, 08:33 PM)Xfurry Wrote: Well, I'm not a very big fan of cmake. This is mostly because it breaks the folder structure that we have in Visual Studio, and all the files will be in disorder. (this is actually the only reason).

I suppose that working with property sheets, involves something like this: https://msdn.microsoft.com/en-us/library/669zx6zc.aspx right?

"fixing" (or let's say, aligning it with the current VS behaviour) the output folder structure of our current cmake project would remove a big part of the concerns of Xfurry, Schmoozerd & co. about removing the SLNs.
Reply
Post: #15
Guys, I think the discussion about project structure in Visual Studio is wrong.

1. generating from CMake and only having to maintain one build system is a greater benefit.
2. you can modify the folder structure generated by CMake for both Visual Studio and als Xcode. This requires 10 lines of CMake to do as a macro.

As a final word, I would also like to suggest to think about the current CMake build definitions used by CMangos. They are violating quite a lot of principles of CMake, and for now will lead to issues.

1. do not rely on hard coded stuff in CMake, try to use provided packages, everything needed is in there since CMake 2.8.12.
2. abstract platform and compiler handling.
3. abstract library handling and make using external libraries a priority

It would be possible to replace the build system with something that works Windows, Linux, Mac OS and BSD, and is usable on all core branches, and work needed is like two or three days.

Anyway... folder structure discussion is moot, as it can be customized, and this is an official feature of CMake.
Reply
Post: #16
Here is an update from my side.

As we discussed yesterday, I tried uninstalling Visual Studio 2013 and installing Visual Studio 2015.
So now, I have VS 2015 and boost 1.59 for VC14.

However, similar to VS 2013, the linking error it's still there.
So I think this cannot be related to the version of VS or to VS itself. Maybe it's something related to the boost prebuild binary that it's available to install from the website, or maybe some other windows / systemproblem.

Code:
Severity    Code    Description    Project    File    Line    Suppression State
Error    LNK1104    cannot open file 'libboost_system-vc140-mt-1_59.lib'    mangosd    C:\..\Cmangos\workcore-wotlk\win\VC140\LINK    1    
Error    LNK1104    cannot open file 'libboost_system-vc140-mt-1_59.lib'    realmd    C:\..\Cmangos\workcore-wotlk\win\VC140\LINK    1
Reply
Post: #17
(03-03-2016, 04:40 PM)Xfurry Wrote: Here is an update from my side.

As we discussed yesterday, I tried uninstalling Visual Studio 2013 and installing Visual Studio 2015.
So now, I have VS 2015 and boost 1.59 for VC14.

However, similar to VS 2013, the linking error it's still there.
So I think this cannot be related to the version of VS or to VS itself. Maybe it's something related to the boost prebuild binary that it's available to install from the website, or maybe some other windows / systemproblem.

Code:
Severity    Code    Description    Project    File    Line    Suppression State
Error    LNK1104    cannot open file 'libboost_system-vc140-mt-1_59.lib'    mangosd    C:\..\Cmangos\workcore-wotlk\win\VC140\LINK    1    
Error    LNK1104    cannot open file 'libboost_system-vc140-mt-1_59.lib'    realmd    C:\..\Cmangos\workcore-wotlk\win\VC140\LINK    1

I have the same trouble too, plus error boost/asio.hpp - Running windows 10
[Image: maxcard.jpg]
Reply
Post: #18
So now that iam confident that CMAKE can generate a perfect sln/project for us i also confident that "extra users" step will be able to reduce total number of steps for each users.
We can automatize lot of thing with it.

But well, there is one more thing to do before working on it. Removing ACE.
Reply
Post: #19
For those who still have problem please follow this steps ->https://oldforum.cmangos.net/thread-7362...l#pid45571 and repull latest revision.
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  [proposal] Project cmangos-bot cleanup Wingblade 2 731 11-22-2016, 11:31 AM
Last Post: HanFox
  Drop Windows 32 bit support? namreeb 18 5,768 05-07-2016, 03:37 AM
Last Post: namreeb
  vc8, 9, and 10 files in dep/ACE_wrappers alysher 2 1,467 09-22-2015, 11:19 PM
Last Post: alysher
Question Large Player races on mounts unable to pass low entrances: core or client issue? tarwyn 6 5,205 12-27-2014, 04:48 PM
Last Post: Velvet
Question [Proposal] Drop VC90 support Xfurry 32 17,008 12-01-2014, 12:25 PM
Last Post: Xfurry
  cmake compiling alexluana 13 13,513 03-04-2013, 03:34 PM
Last Post: alexluana

Forum Jump:


Users browsing this thread: 1 Guest(s)

Continued MaNGOS | Return to Top | | Lite (Archive) Mode | RSS Syndication