Page 1 of 1

libfilezilla project is unloaded in the solution when building for Visual Stuio 2019

Posted: 2020-03-26 16:44
by odiee
Hi.

I downloaded libfilezilla-0.20.2.tar.bz2 from the project page and extracted it.
The base folder is provided with the VS Solution that will show the demo projects correctly but the lib project it self is visible but not loaded (it says so).

I tried to find if there are some additional steps for compiling, but didn't find anything.

Am I missing something here?

I'm using win10 64 with VS-community-2019

Re: libfilezilla project is unloaded in the solution when building for Visual Stuio 2019

Posted: 2020-03-27 15:57
by botg
The recommended way to use the library under Windows is through MinGW-w64 as distributed with MSYS2.

Re: libfilezilla project is unloaded in the solution when building for Visual Stuio 2019

Posted: 2020-03-27 19:57
by odiee
I know. But that doesn't really work for me as I need to compile it all with VS.
The first step which would be to compile libfilezilla.

But I figured that the problem is in the missing dependencies.props file that comes with the server and client apps but not with libfilezilla.
This file comes with the client and the server and serves as a placeholder to input paths to other dependencies.

Maybe someone forgot to include it in the project source of the lib?

Re: libfilezilla project is unloaded in the solution when building for Visual Stuio 2019

Posted: 2020-08-30 23:11
by mfstanton
there is a dependencies.props.example file in the Filezilla Server source file. It appears things fall back into place if you rename it without the "example" postfix and copy that file into your folder. It is a workaround i have tried in the server source. It requires other file tailoring

Re: libfilezilla project is unloaded in the solution when building for Visual Stuio 2019

Posted: 2020-08-31 14:46
by mfstanton
It is a separate download from the SVN (Subversion) database. I found it yesterday and am now struggling with it to build under VS It does not come with the Dependencies.props file either so i am looking at the Server App to figure it out