>>Jan Ehrhardt's XP test was really slow and if we exclude that from the
>>results, the average patched result goes down to 46%.
Perhaps completely irrelevant and probably already taken into account: Windows
(any network performance) may severely suffer from a virus scanner,
or if no AV or
>I get the following errors when I try to build the project:
>1>project.obj : error LNK2001: unresolved external symbol __imp_curl_easy_init
>1> project.obj : error LNK2001: unresolved external symbol
>__imp_curl_easy_setopt
>1> project.obj : error LNK2001: unresolved external symbol
>
> > 1. solution files
> > 2. cmake
> > 3. nmake
>
> and...
>
>4. configure (msys/mingw)
>5. Borland makefiles
>6. mingw makefiles
>
> > I understand that 'everybody is liking his own preferred method' (in my
> case
> > #3), but it also makes that the few maintainers/contributors
> Any takers?
>
> I do a lot of stuff in this project. I merge something like 80% of all commits
> and I (currently) author around 60% of all commits. I do this because I think
> it's fun and I enjoy doing it. And I feel that know the technologies involved.
>
> There are however two specific
>
> The -c option might help. You can use it to provide a path to your curl
> executable:
> https://curl.haxx.se/dev/runtests.html
>
Thanks Marcel, but for now, I will skip the tests on Windows. First try to get
the other things working
> Strawberry Perl didn't work for me last time I tried it.
> testcurl.pl could work with Cygwin's Perl since a proper
> fork() function is needed.
In a Windows prompt, not having make is the first problem.
And the expected build location (../src/bin) is another problem,
As curl.exe is in
>
> At least Windows 2000 still should be supported because the original MinGW
> targets it by default and quite a few people are using it because it appears
> in
> Google search results before the more current and more complete MinGW-
> w64.
>
Then I'll leave as it is. But I'm then still a
Hi,
Is anyone still using Visual Studio 6 for the cURL winbuild\Makefiles?
If VS6 can be dropped, then the VC= can probably be dropped from
winbuild\MakefileBuild.vc, and instead of it an output directory can be used
(in winbuild\Makefile.vc).
That case is probably useful for the case that
thod).
>
> you need a Unix-style shell for that, like MSYS2. I believe that if you use
> the
> CMake build,
> the tests are built too. Then you should hopefully be able to run them via
> runtests.pl, but
> I've only ever done that when building directly inside the MSYS or Cygwin
> shell via the
>
> Which method do you use?
>
As said in my previous email: winbuild.
Which is actually nmake + a Makefile.
---
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Hi,
Does cURL on Windows have tests, similar to the check target on *NIX flavors?
I like to validate the outcome of a build (and I'm not using the winbuild build
method).
Kees
---
Unsubscribe:
> If they weren't, how did the windows stuff in there get introduced in the
> first place?
From past discussions, discussions about proposed changes for Windows builds
did not end in
a clear decision. That's why I now have made a very simple fix.
> That said, I'm personally not a windows
axx.se] On Behalf Of
> Kees Dekker
> Sent: Wednesday, March 21, 2018 11:01
> To: libcurl development <curl-library@cool.haxx.se>
> Subject: RE: curl Windows build and setenv command
>
> And may be useful additional information:
>
> I'm now calling the build scripts in
bs. That's also why the link /lib command in the makefile is incorrect
(as in accumulates all static libs in one libcurl.lib).
Kees
> -Original Message-
> From: curl-library [mailto:curl-library-boun...@cool.haxx.se] On Behalf Of
> Kees Dekker
> Sent: Wednesday, March 21, 20
t; You can see what it looks like at
> https://github.com/richardthe3rd/curl/tree/windows_zlib_locations
>
> Richard
>
>
> On 20 March 2018 at 15:57, Kees Dekker <kees.dek...@infor.com> wrote:
> > Hi,
> >
> >
> >
> > In
> https://github.com/curl/c
Hi,
In https://github.com/curl/curl/blob/master/winbuild/BUILD.WINDOWS.txt
something is told about setenv, however, recent Windows versions do not have a
setenv command and neither has the Visual Studio command prompt (I'm using
Visual Studio 2015 on Windows 10 and/or Windows Server 2012 or
Hi,
>I need static libcurl.lib which uses static OpenSSL but does NOT contain it as
>part of itself. Otherwise I would get link errors (symbol conflicts) when
>building VirtualBox with both libcurl AND openssl. The first scenario gave me
>exactly what I needed, but now in 7.54.0 it is
>
> On Fri, 20 Jan 2017, Kees Dekker wrote:
>
> > I will try to do so. But it will take time (set this on my todo list).
I thought I have create a small fix, that was read and checked by Rod. Again
making new (smaller) diffs means that I've to start again.
AFAIK the only thing left
://
On 23.01.2017 16:55, Kees Dekker wrote:
> Sorry, I don't understand. Do you mean that curl 7.52.1 should also work?
> If I understood well, I have to wait for a fix that is in 7.53.0, isn't it?
> I now got CURLE_URL_MALFORMAT when passing the following URL:
> "file://w:/general/
nuary 23, 2017 13:04
To: libcurl development <curl-library@cool.haxx.se>
Subject: RE: broken cURL on semicolon (of Windows drive letter) in
file://
On Mon, 23 Jan 2017, Kees Dekker wrote:
> I think if drive letters are again supported, then this fix Is appropriate.
Drive lettes were su
BTW: the subject of the mail is wrong, semicolon had to be colon, sorry.
-Original Message-
From: curl-library [mailto:curl-library-boun...@cool.haxx.se] On Behalf Of Kees
Dekker
Sent: Monday, January 23, 2017 09:45
To: libcurl development <curl-library@cool.haxx.se>
Subject: RE:
.se>
Subject: Re: broken cURL on semicolon (of Windows drive letter) in
file://
On Fri, 20 Jan 2017, Kees Dekker wrote:
> I discovered that cURL 7.50.1 did accepts, but cURL 7.52.1 did not accept a
> colon in an URL. Example: the following URL did not work:
> file://c://temp/test.xml
Oka
Hi,
I discovered that cURL 7.50.1 did accepts, but cURL 7.52.1 did not accept a
colon in an URL. Example: the following URL did not work:
file://c://temp/test.xml.
I also discovered that back slashes are not allowed anymore (may be related to
https://github.com/curl/curl/issues/1007). That is
I will try to do so. But it will take time (set this on my todo list). If you
have any wishes or suggestions, please let me know. I can't promise a date
whenever I've something ready (I'm still busy to get all working of our own
product, that uses cuRL (and OpenSSL + for Windows also zlib and
Is this a question to me to provide information to the help text? (Note that
this is the first time I was involved in this mailing list, I don't know the
procedure how a fix/patch get applied.
And next time I will try to make a git pull request. Sorry for the
inconvenience this patch caused for
But the old style Makfile.vc did not produce such long paths. In that case
I had something like lib\debug-ssl-ssh2-zlib. Pretty much shorter.
With the winbuild procedure I get:
winbuild\..\builds\libcurl-vc14-x86-debug-static-ssl-static-zlib-static-ssh2-static-ipv6-sspi-obj-lib\.
If this
Thanks. If you like, and if I've time, I would not completely begin of scratch,
but write much together the common practice on UNIX.
Normally, a user that likes to use cURL, would (IMO) build the cURL flavor
wanted (with or without zlib, with or without openSSL etc).
I.e. finally, one output is
...@cool.haxx.se] On Behalf Of
Daniel Stenberg
Sent: Monday, January 16, 2017 18:52
To: libcurl development <curl-library@cool.haxx.se>
Subject: Re: proposed changes for winbuild makefile
On Mon, 16 Jan 2017, Kees Dekker wrote:
> I've attached a patch to address some issues in the Windows build.
will file a different patch.
From: curl-library [mailto:curl-library-boun...@cool.haxx.se] On Behalf Of Kees
Dekker
Sent: Monday, January 16, 2017 09:32
To: curl-library@cool.haxx.se
Subject: proposed changes for winbuild makefile
Hi,
I've attached a patch to address some issues in the Windows
e. If no makefile variables are specified to override libraries
names and/or include or library paths, then the defaults fall back to the
original behavior.
This is my first contribution to this mailing list. Not sure whether all
information is provided. The patch is in *NIX style format and ca
30 matches
Mail list logo
