Thanks for the prompt reply!

So that's good to know, I was trying to build 3.21.5 - but it is in that 
version that I am missing autogen.sh.
I could try downgrading to 3.20.3 if that changes things.

Also, I am not opposed to using cmake either but I cannot for the life of 
me figure out how to get cmake to not use MSVC. I need to build libprotobuf 
withh gcc/cygwin but when I run cmake it just ignores my toolchain file and 
always goes back to MSVC 2019.

Thanks!
Davorin

On Wednesday, November 2, 2022 at 12:58:04 PM UTC-7 [email protected] 
wrote:

> We have actually removed support for the autotools build, and 3.21 was the 
> last release that supported it. If you want to avoid Bazel then I would 
> recommend using CMake, since we will continue supporting CMake in future 
> releases.
>
> On Wed, Nov 2, 2022 at 12:29 PM Davorin Mista <[email protected]> 
> wrote:
>
>> Since I cannot figure out how to get bazel to not use MSVC I want to try 
>> building using autoconf/automake but I'm missing the initial "autogen.sh" 
>> referenced by the README.md in the src folder.
>> How do I get autogen.sh as mentioned in src/README.md or at least 
>> configure.ac which is normally used for automake?
>>
>> -- 
>>
> You received this message because you are subscribed to the Google Groups 
>> "Protocol Buffers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/protobuf/e1ab9e1d-5b99-446f-905b-6bf14b98ccfdn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/protobuf/e1ab9e1d-5b99-446f-905b-6bf14b98ccfdn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/protobuf/775a6a88-80bb-4a63-94d7-4415ead1b0b3n%40googlegroups.com.

Reply via email to