Official eMule-Board: Guide To Compile Emule 0.60A - Official eMule-Board

Jump to content


Page 1 of 1

Guide To Compile Emule 0.60A

#1 User is offline   shinjiinii 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 4
  • Joined: 13-October 20

Posted 13 October 2020 - 08:27 PM

Hi,
I'm very new to Emule forum, so thank for your work! I was trying to compile the just released version 0.60a on my PC (windows 10 / Visual Studio 2019). However, Visual Studio refuses to fully open the project. I know VS2019, but I'm habit to use C# (.NET, nuget as package manager), so I don't know which are the dependencies or external libraries to be installed to compile emule. May you link a guide to make this?
The error is:

C:\Users\fab\workspace_vs\eMule\CxImage\cximage.vcxproj : error : not possible to load the project file. Unable to find the path 'C:\Users\fab\workspace_vs\eMule\CxImage\cximage.vcxproj'. C:\Users\fab\workspace_vs\eMule\CxImage\cximage.vcxproj

and it is repeated for all the subprojects.
0

#2 User is offline   shinjiinii 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 4
  • Joined: 13-October 20

Posted 18 October 2020 - 07:52 PM

I can confirm that I can't compile even after the "new" v0.60a release (wasn't released a week ago?). Opening visual studio 2019, there are not the side project like zlib, id3lib and so on. Screenshot of the solution bar: ibb.co/8DV9M25
0

#3 User is offline   megaT 

  • Member
  • PipPip
  • Group: Members
  • Posts: 41
  • Joined: 09-May 20

Posted 18 October 2020 - 07:57 PM

Well you need to get a lil' bit into how C++ projects are being compiled and dependencies are satisfied (which is totally different from how its done in .NET/C#)
See my post: https://forum.emule-...howtopic=165205

I dont think its any different with eMule v0.60,
you can simply gather the dependencies on the net and setup your own project.
0

#4 User is offline   shinjiinii 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 4
  • Joined: 13-October 20

Posted 19 October 2020 - 08:05 PM

Thanks for the hint:)

I had read your post, and I tried to manually download the first library (libpng). I had gone for the 1.6.37 (same of yours), but in the zip there is a different structure: VC2019 asks for libpng\projects\visualc\libpng.vcxproj, but in the archive I can find only libpng\projects\visualc71\libpng.vcproj.

Should I navigate through all the versions of libpng and guess for the right version?

Here the link where I found the lib archive.

sourceforge.net/projects/libpng/files/libpng16/1.6.37/
0

#5 User is offline   megaT 

  • Member
  • PipPip
  • Group: Members
  • Posts: 41
  • Joined: 09-May 20

Posted 19 October 2020 - 09:06 PM

Well there is libpng\projects\vstudio\vstudio.sln or not?
That's the solution file you're looking for, its also always good to always read INSTALL or Readme instructions.

Quote

C2019 asks for libpng\projects\visualc\libpng.vcxproj...

You dont need to take that for granted, the msbuild stuff is horrible ancient,
maybe they are building against a different version.
Where all the dependencies is, isnt really abstracted in any way.
You can unload it and reload the fitting pieces, or simply exclude those from the main solution anyways -
you dont need to ever rebuild them again.
Its sufficient if you link against the proper libraries.

This post has been edited by megaT: 19 October 2020 - 09:13 PM

0

#6 User is offline   shinjiinii 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 4
  • Joined: 13-October 20

Posted 25 October 2020 - 07:59 PM

View PostmegaT, on 19 October 2020 - 09:06 PM, said:

Well there is libpng\projects\vstudio\vstudio.sln or not?
That's the solution file you're looking for, its also always good to always read INSTALL or Readme instructions.

Quote

C2019 asks for libpng\projects\visualc\libpng.vcxproj...

You dont need to take that for granted, the msbuild stuff is horrible ancient,
maybe they are building against a different version.
Where all the dependencies is, isnt really abstracted in any way.
You can unload it and reload the fitting pieces, or simply exclude those from the main solution anyways -
you dont need to ever rebuild them again.
Its sufficient if you link against the proper libraries.



Ok thanks for the answer, just a bit different from what nowadays we are habit (npm, nuget, and whatsoever package manager) :thumbup:
0

  • Member Options

Page 1 of 1

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users