EQLaunch compile
 

So, I normally run on Linux and don't really have compile issues there, but I decided to put a windows compile together to see if I could do some testing. I got all the pieces to compile except for EQLaunch. I know that it has something to do with my set up. But I can't figure out what. It's failing in the linker with:

I do have WinPcap installed in that location, but it shouldn't be even looking at that stuff. I've poured through the configuration of the solution and can find no reference to this. I've completely removed the solution, downloaded it over again and still I get this. I'm hoping that one of you that has more experience with Visual C++ can help me target where my issue is. I'm using Visual C++ Pro 2008 if that helps.

Well, I'm not familiar with WinPcap, but the "WpdPack\Lib;.obj" reference is most likely not a valid filename.

The question needing to be figured out is... is the linker actually looking for "WpdPack\Lib.obj" and there's a stray semicolon in the project settings, or is it looking for "WpdPack\Lib\[Something].obj" and a filename is missing in the project settings?

If it looks like there is a Lib.obj file in the WpdPack folder, I would suggest looking through the project properties for a reference to "Lib;" and get rid of the semicolon.

If it looks like there is a Lib folder inside WpdPack instead, it may be a little more tricky to look through the settings or make file and figure out what filename is being cropped out and how.

- Shendare

That's the problem. I've looked everywhere for this reference in the configs and I can't find it. If I could find it, I could remove it since it's not needed for the Launcher. That's the thing I was hoping someone could tell me where to look in the config. It happens using both the Release and the Debug configuration. I know it's my setup but I can't figure out where it's getting this from.

Andrew80k try this: http://support.microsoft.com/kb/815645. Basically it says that VS Managed C++ can't handle spaces in the path statements. Whether it is managed or not shouldn't have anything to do with it handling spaces. You can check and see if there is a space in the path and see what happens.

I figured it out. Still not entirely sure where it came from, but I made it not inherit link properties from parent and it removed that junk and linked. So I'm good. Thanks for the help.