autoantwort comments

Results 120 comments of


                                            autoantwort

Create only one target

Yeah that should be supported. What I means was _*build* a static and dynamic variant of libuv simultaneously_ not _install a static and dynamic variant of libuv simultaneously_

Create only one target

Like this: ```bash cmake -B build -DBUILD_SHARED_LIBS=OFF cmake --build build cmake --install build cmake -B build -DBUILD_SHARED_LIBS=ON cmake --build build cmake --install build ```

[curl] Requesting [core,mbedtls] still builds and depends on openssl

This is not possible until something like https://github.com/microsoft/vcpkg/pull/22216 gets implemented since these feature are options and not additive

[<vcpkg was unable to detect the active compiler's information. See above for the CMake failure output.>] build failure

> error: vcpkg was unable to detect the active compiler's information. See above for the CMake failure output. And what did reading the logs reveal?

ompl[app] build failure

> Vcpkg version: 2020.06.15-nohash This is a very old version. Update your vcpkg version by running `git pull`

[vcpkg] Controlling top-level find_package

> We do want something like this but haven't had time to seriously look yet :(. Thanks! @BillyONeal Do you maybe now have time to do it? :)

[vcpkg] Controlling top-level find_package

> The second commit adds variable (template) `CMAKE_FIND_PACKAGE_` which I guess you mean `VCPKG_FIND_PACKAGE_`?

CMake: build either static or shared + don't force PIC + add ALIAS targets

> Hi @SpaceIm , any chance of getting this rebased on current master? Thanks I have created #1160 for that.

enforce_atomic decorator for commit callbacks to workaround MySQL limitations

Maybe one could create a feature request at the django project for a `pre_commit` callback. Edit: Ok that would not help since there are no django transactions in auto commit...

enforce_atomic decorator for commit callbacks to workaround MySQL limitations

And that does not cover all cases. You can change an object without calling save. For example by calling [update](https://docs.djangoproject.com/en/4.2/ref/models/querysets/#django.db.models.query.QuerySet.update)