Displaying 20 results from an estimated 1000 matches similar to: "How to build xapian 1.4.10 with MSVC2017"
2019 Feb 21
1
How to build xapian 1.4.10 with MSVC2017
Thank you very much,It works!
And some Q&A I meet,may help somebody:
1. If zlib build with 32bit,should use MSVC's 'vcvars32.bat';
2. Add '-Z7' to CXXFLAGS can release *.pdb file for VS2017 'Step Into' debug, such as: CXXFLAGS="-EHsc -Z7";
3. If Somebody write a demo in VS2017
3.1 change libxapian.a's name to libxapian.lib;
3.2 make sure the
2019 Feb 20
1
How to build xapian 1.4.10 with MSVC2017
hi, I have read the install document,https://github.com/xapian/xapian/blob/v1.4.10/xapian-core/INSTALL,but don't how to build xapian project by MSVC.
I execute command in mingw64.exe: ./configure CC="cl -nologo" CXX="$PWD/compile cl -nologo" CXXFLAGS=-EHsc AR=lib
has some errors:
# ./configure CC="cl -nologo" CXX="$PWD/compile cl -nologo" CXXFLAGS=-EHsc
2019 Feb 21
0
How to build xapian 1.4.10 with MSVC2017
On Wed, Feb 20, 2019 at 12:41:07PM +0800, cswuyg wrote:
> Thanks for your reply.
> I had run vcvars64.bat,but still cann't find 'cl'.
> Finally I fix it, change msys2_shell.cmd: "if it is present: replace rem set MSYS2_PATH_TYPE=inherit with set MSYS2_PATH_TYPE=inherit".
OK, I'll note that in the instructions.
It looks like you can also enable this option as a
2019 Feb 22
0
How to build xapian 1.4.10 with MSVC2017
> Great, but which "it" worked?
I had install mingw earlier, but not set it to $PATH, so must be 'LD=link' and your previous advices on "CXXFLAGS" .
I execute configure like this:
./configure LD=link CC="cl -nologo" CXX="$PWD/compile cl -nologo" CXXFLAGS="-EHsc -Z7" AR=lib CPPFLAGS=-IC:/zlib-1.2.3-lib/include
2004 Oct 12
3
[LLVMdev] Showstopper on Visual C
Hi all,
Well, suggestion for workarounds for the namespace problems are
welcome... this is a 7 minutes compile files on a pentium 4 3ghz 700Mb
ram...
The fatal error at the end MAY depend on the previous... or at least, I
hope so.
cl /nologo /TP /EHsc /GR /Zi /Yd /D__STDC_LIMIT_MACROS
/DHAVE__FINITE_IN_FLOAT_H /DHAVE__ISNAN_IN_FLOAT_H
/ISTLport-4.6.2\stlport /Illvm\inc
lude
2014 Oct 02
2
[LLVMdev] Header File Not Found?
I'm having a strange problem compiling with VS 2013. It's not finding a
header file that's there in one of the header file search dirs.
Here's the compile command (with the names changed to protect the
innocent ;-)
1> C:\Program Files (x86)\LLVM\msbuild-bin\CL.exe /c
/IC:\[top-level-dir]\[source-dir]\
/IC:\[top-level-dir]\[source-dir]\[sub-dir-1]
2014 Oct 23
2
[LLVMdev] compiler-rt with MSVC 2013
compiler-rt libs must be built with /MT, so the MSVS build is doing
the wrong thing here.
2014-10-23 12:52 GMT-07:00 Aaron Ballman <aaron at aaronballman.com>:
> On Thu, Oct 23, 2014 at 3:42 PM, Aaron Ballman <aaron at aaronballman.com> wrote:
>> On Thu, Oct 23, 2014 at 3:38 PM, Aaron Ballman <aaron at aaronballman.com> wrote:
>>> On Thu, Oct 23, 2014 at 2:57
2015 Jul 24
2
[LLVMdev] [lldb-dev] [3.7 Release] We have branched
On Fri, Jul 24, 2015 at 12:05 PM, Nico Weber <thakis at chromium.org> wrote:
> On Thu, Jul 16, 2015 at 8:08 AM, Nico Weber <thakis at chromium.org> wrote:
>
>> On Wed, Jul 15, 2015 at 10:45 AM, Russell Wallace <
>> russell.wallace at gmail.com> wrote:
>>
>>> Basic test results on Windows 7, visual studio 2013 (64 bit):
>>>
>>>
2004 Oct 12
0
[LLVMdev] Showstopper on Visual C
struct X86AsmPrinter is in an anonymous namespace, but printInstruction
is declared in namespace llvm. try editing the tablegen output to move
X86AsmPrinter::printInstruction into an anonymous namespace, not llvm.
I suspect this will at least fix the first problem. Then we can figure
out the proper longterm fix.
Andrew
On Tue, 2004-10-12 at 03:56, Paolo Invernizzi wrote:
> Hi all,
>
2015 Jul 16
2
[LLVMdev] [lldb-dev] [3.7 Release] We have branched
On Wed, Jul 15, 2015 at 10:45 AM, Russell Wallace <russell.wallace at gmail.com
> wrote:
> Basic test results on Windows 7, visual studio 2013 (64 bit):
>
> Build clang with visual studio - okay
>
> Build clang with itself - okay
>
> Build Python - okay
>
> Build Ruby - fails on conftest.c, but 3.6 also failed so this is not a
> regression bug
>
> Build
2020 Mar 27
3
Exceptions on Windows & MSVC
Here is a wiki page and git repo with an implementation of SEH that passes
all the tests for x86.
We're looking for feedback before putting a patch on Phabricator.
https://github.com/tentzen/llvm-project
https://github.com/tentzen/llvm-project/wiki
On Mon, Nov 18, 2019 at 10:59 PM Gaier, Bjoern <Bjoern.Gaier at horiba.com>
wrote:
> Thank you for this Aaron!
>
>
>
> In
2015 Jul 24
0
[LLVMdev] [lldb-dev] [3.7 Release] We have branched
On Thu, Jul 16, 2015 at 8:08 AM, Nico Weber <thakis at chromium.org> wrote:
> On Wed, Jul 15, 2015 at 10:45 AM, Russell Wallace <
> russell.wallace at gmail.com> wrote:
>
>> Basic test results on Windows 7, visual studio 2013 (64 bit):
>>
>> Build clang with visual studio - okay
>>
>> Build clang with itself - okay
>>
>> Build Python
2014 Oct 23
2
[LLVMdev] compiler-rt with MSVC 2013
On Thu, Oct 23, 2014 at 3:38 PM, Aaron Ballman <aaron at aaronballman.com> wrote:
> On Thu, Oct 23, 2014 at 2:57 PM, Aaron Ballman <aaron at aaronballman.com> wrote:
>> On Thu, Oct 23, 2014 at 2:46 PM, Timur Iskhodzhanov <timurrrr at google.com> wrote:
>>> 2014-10-23 11:34 GMT-07:00 Aaron Ballman <aaron at aaronballman.com>:
>>>> On Thu, Oct
2006 Apr 21
2
error in abld build wins udeb
I am trying to compile speex.1.1.12 for Symbian OS but I get lots of
errors:
C:\Programmi\Symbian\7.0s\Series60_v21\Series60Ex\speex-1.1.12\symbian>abld
buil
d wins udeb
make -r -f
"\Programmi\Symbian\7.0s\Series60_v21\EPOC32\BUILD\PROGRAMMI\SYMBI
AN\7.0S\SERIES60_V21\SERIES60EX\SPEEX- 1.1.12\SYMBIAN\EXPORT.make" EXPORT
VERBOSE
=-s
Nothing to do
make -r -f
2017 Sep 04
2
how to build Xapian project on windows?
> It's close to irrelevant when they last worked at this point - the current
> stable release series is 1.4.x, and they definitely won't work with that.
acknowledged
Visual Studio 2008, win32 makefiles (from C. Hull's website)
and xapian-core-1.2.8 are mentioned together on this webpage
https://lists.xapian.org/pipermail/xapian-devel/2012-October/001883.html
2006 Aug 22
4
Native Extensions on Windows 0.10 series
Hi all,
I''ve just noticed that 0.10 is out and wanted to give it a try on windows.
I''m not at all an VS C++ Developer so I might do something very stupid here.
My env: Windows Server 2003
VS .NET 2003
On the command line with nmake from VC7 in the path this is what I get:
Attempting remote update of ferret
Building native extensions. This could take a while...
Microsoft
2015 Mar 09
2
[LLVMdev] LLVM 3.6: problems building on Windows using MSVC 2013
Hi,
I have been using LLVM+Clang in my project for some time and it has been
working just fine up to now (I am currently using version 3.5.1).
However, with version 3.6 having just been released, I thought I would give
it a try and update my code to use MCJIT rather than the now discontinued
JIT. Well, this proved to be a relatively smooth process, and everything is
now working fine on
2015 Feb 20
2
[LLVMdev] Building Compiler-RT on Windows
Has anyone built Compiler-RT on Windows? I am attempting to compile it for
ARM, but I get errors from CMake. It appears to be trying to pass VC++
flags to Clang. I am using a version of Clang built from trunk.
PS D:\llvm\arm_test\compiler-rt-build> cmake -G Ninja
-DCMAKE_C_COMPILER=clang.exe -DCMAKE_CXX_COMPILER=clang++.exe -DCM
AKE_RC_COMPILER=rc.exe -DCMAKE_CXX_FLAGS=""
2019 Nov 11
4
Exceptions on Windows & MSVC
At Microsoft we open sourced some of our compiler tests for exception
handling on github.
https://github.com/microsoft/compiler-tests
We are looking into what it would take to get these to work with clang-cl.
I’m planning to share a design document on the mailing list soon.
Aaron
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2019 Feb 18
2
lld-link fails to link 32bits assembly functions but 64bits pass
Hi Rui, Peter,
You know I'm enabling the "clang-cl + lld-link" toolchain for Uefi firmware. I meet a problem that the lld-link fails to link 32bits assembly functions, but can link 64bits assembly functions successfully. I need your suggestion.
Below is an example to show my problem in linux. The example has two only source files: main.c and foo.nasm.
$ cat main.c
void Foo (void);