kicad-developers team mailing list archive

[Dick Hollenbeck <dick@xxxxxxxxxxx>]

I assumed the doctored file was directly useable.  Since that is not the
case, would you prefer preparing a proper archive without symlinks? Then
put that someplace else?  In the case of avhttp I brought the zip into our
source tree, but I am viewing that as temporary until cmake has https
download capabilty. It does already, but we all use older versions.
On Oct 16, 2013 6:14 AM, "Brian Sidebotham" <brian.sidebotham@xxxxxxxxx>
wrote:

> On 16 October 2013 12:04, Dick Hollenbeck <dick@xxxxxxxxxxx> wrote:
>
>> On windows, can you try downloading from github the doctor-ed zip file
>> like the person in the bug report said?  Lets put that bug report URL in
>> our download script too as a comment.
>>
>
> Okay, I will do that.
>
> The zip file is awkward. It simply has nothing in place of the symbolic
> links, so the include directory is empty. I can modify the cmake scripts to
> populate it when it doesn't exist, or the patch can contain the include
> files. In the latter case the patch sits around 1.5Mb!
>
> I think I'll do the magic in the CMake script to populate the include
> directory if it is empty, and our patch step will apply the CMake files
> only. I'll add the bug report URL into our download_openssl.cmake too. It's
> a shame, it just makes a neat External_Add into a mess of if( MINGW ) crap.
>
> Ideally I wanted this CMake build system to work on top of the .tar.gz so
> it could be a common build step for all platforms.
>
> Best Regards,
>
> Brian.
>
>