search for: jinja2cpp

...dantic -m64 -D_SILENCE_CXX17_ADAPTOR_TYPEDEFS_DEPRECATION_WARNING -Dvariant_CONFIG_SELECT_VARIANT=variant_VARIANT_NONSTD -D_SILENCE_CXX17_ALLOCATOR_VOID_DEPRECATION_WARNING -D_CRT_SECURE_NO_WARNINGS -D_WINSOCK_DEPRECATED_NO_WARNINGS -D_WIN32 -D_WIN32_WINDOWS -D_NDEBUG -D_MBCS -IC:/boost_1_68_0 -IC:/Jinja2Cpp/install_x64/include -IC:/json/single_include -LC:/boost_1_68_0/stage/lib/libboost_system-vc141-mt-x64-1_68.lib -LC:/Jinja2Cpp/install_x64/lib/static/jinja2cpp.lib currency_converter.cpp -o currency_converter.exe " But I have still have linker errors from Jinja2Cpp and Boost.System. Jinja2Cpp...

I already mentioned what flag I tried. It's in the first email in this thread. And I want to link against Boost.System and the Jinja2Cpp library (the latter's documentation can be found here: https://github.com/flexferrum/Jinja2Cpp . And I also have some GUI applications using FLTK as well that I want to try to build using LLVM as well, so I'll have to know how to link against FLFK's libraries too. [https://avatars3.git...

I add the -fuse-ld=lld flag to the compiler command line itself. And I included LLD when I built LLVM (I checked out the mono repo and built that version). What command line arguments should I pass to LLD when I want to link against third-party libraries? That's what I'm asking. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Osman Zakir <osmanzakir90 at hotmail.com> writes: > LLVM on a Developer Command Prompt. I don't know what you mean by that. "LLVM" isn't a command. Can you post the exact command you use to link? > The ones I want to fix first are the ones from Boost and Jinja2Cpp. I > saw some from those as well. I'm not at all familiar with Jinja2Cpp. Is it possible it needs some explicit template instantiations? > If there any standard library ones missing, could it be because I > couldn't get it to build libcxx? I did try to include that, but it >...

.... And I'm using Windows, so I > shouldn't use LDFLAGS or CXXFLAGS as environment variables. I'll use > them directly on the compiler command line instead. The libraries I > need to link against are > C:/boost_1_68_0/stage/lib/libboost_system-vc141-mt-x64-1_68.lib and > C:/Jinja2Cpp/install_x64/lib/static/jinja2cpp.lib. > > I tried to build it with this flag: > " > clang++ -std=c++17 -Wall -pedantic - > D_SILENCE_CXX17_ADAPTOR_TYPEDEFS_DEPRECATION_WARNING - > Dvariant_CONFIG_SELECT_VARIANT=variant_VARIANT_NONSTD - > D_SILENCE_CXX17_ALLOCATOR_VOID_DEPR...

I couldn't get it to build libcxx... You need c++ and c++abi to compile c++ code. On Wed, Dec 12, 2018, 07:01 Osman Zakir via llvm-dev < llvm-dev at lists.llvm.org> wrote: > LLVM on a Developer Command Prompt. The ones I want to fix first are the > ones from Boost and Jinja2Cpp. I saw some from those as well. > > If there any standard library ones missing, could it be because I couldn't > get it to build libcxx? I did try to include that, but it seems to be > missing. What should I do? > ------------------------------ > *From:* David Greene <da...

...r_assign() from C++17). And I'm using Windows, so I shouldn't use LDFLAGS or CXXFLAGS as environment variables. I'll use them directly on the compiler command line instead. The libraries I need to link against are C:/boost_1_68_0/stage/lib/libboost_system-vc141-mt-x64-1_68.lib and C:/Jinja2Cpp/install_x64/lib/static/jinja2cpp.lib. I tried to build it with this flag: " clang++ -std=c++17 -Wall -pedantic -D_SILENCE_CXX17_ADAPTOR_TYPEDEFS_DEPRECATION_WARNING -Dvariant_CONFIG_SELECT_VARIANT=variant_VARIANT_NONSTD -D_SILENCE_CXX17_ALLOCATOR_VOID_DEPRECATION_WARNING -D_CRT_SECURE_NO_WARN...

...it to build libcxx... You need c++ and c++abi to compile c++ code. On Wed, Dec 12, 2018, 07:01 Osman Zakir via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: LLVM on a Developer Command Prompt. The ones I want to fix first are the ones from Boost and Jinja2Cpp. I saw some from those as well. If there any standard library ones missing, could it be because I couldn't get it to build libcxx? I did try to include that, but it seems to be missing. What should I do? ________________________________ From: David Greene <dag at cray.com<mailto:dag a...

...it to build libcxx... You need c++ and c++abi to compile c++ code. On Wed, Dec 12, 2018, 07:01 Osman Zakir via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: LLVM on a Developer Command Prompt. The ones I want to fix first are the ones from Boost and Jinja2Cpp. I saw some from those as well. If there any standard library ones missing, could it be because I couldn't get it to build libcxx? I did try to include that, but it seems to be missing. What should I do? ________________________________ From: David Greene <dag at cray.com<mailto:dag a...

...it to build libcxx... You need c++ and c++abi to compile c++ code. On Wed, Dec 12, 2018, 07:01 Osman Zakir via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote: LLVM on a Developer Command Prompt. The ones I want to fix first are the ones from Boost and Jinja2Cpp. I saw some from those as well. If there any standard library ones missing, could it be because I couldn't get it to build libcxx? I did try to include that, but it seems to be missing. What should I do? ________________________________ From: David Greene <dag at cray.com<mailto:dag a...