Thank you for the quick info. It's clear now. Greetings
Op wo 28 apr. 2021 17:22 schreef Philip Hazel <philip.ha...@gmail.com>: > The CODE_UNIT_WIDTH stuff is concerned with the size of code units in the > data that PCRE2 processes - nothing to do with the 32-bit or 64-bit ness of > the underlying operating system. Just compile in the normal way on a 64-bit > system and you will get a 64-bit library that processes strings of 8-bit > characters. Use the CODE_UNIT_WIDTH settings if you want to process 16-bit > or 32-bit characters. Extraordinarily, this is the second time this week > that this misunderstanding has arisen - I have just been adding some words > to the documentation to try to make it clearer. I didn't think of updating > NON-AUTOTOOLS-BUILD, however, so I will now take a look at that as well. > > Regards, > Philip > > > On Wed, 28 Apr 2021 at 16:07, Chris De Boeck via Pcre-dev < > pcre-dev@exim.org> wrote: > >> Hello, >> >> I just tried to compile PCRE v10.36 on Windows like described in >> 'NON-AUTOTOOLS-BUILD', but when I try to use "-DPCRE2_CODE_UNIT_WIDTH=64" >> there are a lot of errors. >> Is there a way to compile the libraries for 64 bit? I'm especially >> interested in the regex functionality. >> >> Thank you. >> -- >> ## List details at https://lists.exim.org/mailman/listinfo/pcre-dev >> > -- ## List details at https://lists.exim.org/mailman/listinfo/pcre-dev
