Problem linking aseprite

[aer0ace]

I'm building the aseprite solution on Windows 7, Visual Studio 2013 Community. 

I end up with ddraw linker errors. Is there a particular version of the DirectX SDK required for the solution? I see wdxver.c from the allegro project uses SDK version 5, even though there's a mention of DX7 in the comments.

I haven't had any luck installing the old DX versions from 2006, as the files from the MS pages result in a "not a valid Win32 application" error when attempting to launch the installer.

[David Capello]

Hi there!

I’ve used Visual Studio 2013 Professional (which I think it includes the Windows SDK 7.1A, which includes DirectX SDK). Here some info:

http://blogs.msdn.com/b/chuckw/archive/2013/10/03/a-brief-history-of-windows-sdks.aspx

I’m not quite sure where you could download this specific SDK, but maybe you can try:

http://www.microsoft.com/en-us/download/details.aspx?id=8279

Or this one:

https://msdn.microsoft.com/en-us/windows/desktop/hh852363.aspx

Please let me know if you find the specific SDK, I could add the instructions later in the INSTALL.md for Visual Studio 2013 Community.

Good luck and keep in touch!

--
You received this message because you are subscribed to the Google Groups "aseprite-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aseprite-discu...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

- David

[aer0ace]

Okay, I got it working. The latest DirectX(9) SDK  works fine. There is no need to install one of the legacy DXSDKs. My first suspicion was that the projects were targeted for x64, and I was using the cmake GUI to generate the proj files, and noticed that the target was VS2013 64-bit. I didn't know how to change this to force 32-bit, so I just used the cmake commands mentioned in the install instructions. That got past the linker errors, except for one...

Something is setting the path to libcurl.lib to ..\lib\..\. Changing this to ..\lib\ fixed my issue. I'm not familiar with cmake, but I think maybe there's a command that's pointing the library to the wrong path?

[David Capello]

Libcurl was giving some problems.  There is a patch (included after v1.0, in master branch):

https://github.com/aseprite/aseprite/commit/2c408e4c98b9cc0d775309f17100cd0b882f4671

- David