On Thu, Sep 16, 2021 at 8:42 PM austin clifton wrote:
>
> Hi all,
>
> I have an issue which I believe may be a bug. I followed the instructions
> from the "Bug Report" page on the cryptopp wiki and all tests in cryptest.exe
> are passing, so figured I should post here first and make sure it
Say, you have a file that includes Crypto++ headers and needs linking with
Crypto++ library. And Crypto++ is installed into /usr/local.
Then, the following would be sufficient:
clang++ -o my_binary -I/usr/local/include my_source.cpp -L /usr/local/lib
-lcryptopp -lm
(I'm not sure if "-lm" is
I think I'm still misunderstanding the intention of the command.
On Thursday, September 16, 2021 at 3:56:20 PM UTC-7 Jeffrey Walton wrote:
>
> That's an "I" as in "include", bot a lowercase "L".
>
> Use this command:
>
> clang++ -g2 -O3 -I /usr/local/include test.cxx
>
On Thu, Sep 16, 2021 at 6:22 PM Samyukta Yagati wrote:
>
> As a follow up: I tried running
>
> >> clang++ -g2 -O3 -l /usr/local/include /usr/local/lib/libcryptopp.a -WI,-L
>
> And got the error:
> ld: library not found for -l/usr/local/include
> clang: error: linker command failed with exit code
As a follow up: I tried running
>> clang++ -g2 -O3 -l /usr/local/include /usr/local/lib/libcryptopp.a -WI,-L
And got the error:
ld: library not found for -l/usr/local/include
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
It seems like the intention of this
I'm new to using clang, so to clarify: in my case, I should try "clang++
-g2 -O3 -I /usr/local/include cryptopp -Wl,-L" (where cryptopp is a
subdirectory of include)? Also, is "-Wl,/usr/local/lib -o test.exe"
intended to be shorthand for "clang++ -g2 -O3 -Wl,/usr/local/lib -o
test.exe"? (and,
Well, I tested it on another machine at home, but the result remains the
same :(
Benjamin Schäfer schrieb am Donnerstag, 16. September 2021 um 13:37:01
UTC+2:
> I've put a 7z archive with all file I've used into the repository. On the
> CTL I switched the working directory to the extracted
I've put a 7z archive with all file I've used into the repository. On the
CTL I switched the working directory to the extracted one. Then I ran the
following commands:
nmake /f cryptest.nmake
cl.exe /nologo /W4 /wd4231 /wd4511 /wd4156 /D_MBCS /Zi /TP /GR /EHsc
/DNDEBUG /D_NDEBUG /Oi /Oy /O2
I just don't get it. Somehow I can't force the platform toolkit to be used.
It remains at 140, when I compile with cl.exe. Going to the UI of VS2019,
building the library with toolset 142 and cryptolib with 142 produces those
results. When I open the CTL of VS2019 and run the cl.exe command, I
On Thu, Sep 16, 2021 at 4:37 AM Benjamin Schäfer wrote:
> I've made the same steps with nmake and built the library. Then I did the
> same steps with my source file you mentioned, everything on the CTL that came
> with VS2019 (should make no difference).
>
> I uploaded the files here:
>
On Thu, Sep 16, 2021 at 4:37 AM Benjamin Schäfer wrote:
>
> First of all: Thank you for your help and your patience! I really appreciate
> that.
>
> I've made the same steps with nmake and built the library. Then I did the
> same steps with my source file you mentioned, everything on the CTL
First of all: Thank you for your help and your patience! I really
appreciate that.
I've made the same steps with nmake and built the library. Then I did the
same steps with my source file you mentioned, everything on the CTL that
came with VS2019 (should make no difference).
I uploaded the
On Thu, Sep 16, 2021 at 2:44 AM Benjamin Schäfer wrote:
>
> Ok, at least this gives me a ray of hope. So, to get rid of any interfering
> codelines, I did:
>
> - Start Visual Studio
> - New project (MFC Console, static linked MFC, Multibyte (unicode brings up
> the same result)
My Windows
Ok, at least this gives me a ray of hope. So, to get rid of any interfering
codelines, I did:
- Start Visual Studio
- New project (MFC Console, static linked MFC, Multibyte (unicode brings up
the same result)
Full code:
#include
#include
#include "cryptlib.h"
#include "filters.h"
#include
14 matches
Mail list logo
