Hello! > Did this also build the utilities and run any tests? > I just tried that. Tools are built. On CMake, the test fails to link because it uses internal functions not exported by the DLL. So, there is no way to make a working executable, unless you create and link to the static library. With autotools, it is a bit worst because the tests don't even compile if you have not added _GNU_SOURCE to CPPFLAGS.
However, I executed the tests. Most of there were successfull, others were not, but unfortunately the execution blocked with this error: [ FATAL ] /usr/src/debug/gtest-1.15.2-1/googletest/include/gtest/internal/gtest-port.h:1708:: Condition has_owner_ && pthread_equal(owner_, pthread_self()) failed. The current thread is not holding the mutex @0x53a150020 Aborted and here I stopped my test. > Could you please summarize the differences in the files the -devel packages > provide when built under cmake, I attached two screenshots to this email with the differences inspected with winmerge. Into the first screenshot, you can see the differences between the files. As I have written in the previous email, the share directory is missing into my devel package because I moved it in a new package into the "Doc" category. The devel package created from CMake includes also the "cmake" directory with the scripts needed by this tool. The other differences are just "fake", as you can see from the second screenshot. > and could we just add these to the contents of > the -devel package without using that build mechanism, or would we have to > build > and install twice each to get all artifacts? > I have no idea how the config script generated by CMake could be compiled without CMake. Actually, I don't understand why we should do it, since CMake creates everything we need, including the .pc file. > Advice required on ensuring that devel packages that support autotools and > cmake > and make and ninja are built appropriately to provide all of the components to > do all of the above? > > Can we and should we do so when -devel packages also provide cmake support? > As far as I know, CMake and ninja are installed as dependencies of cygport, so I guess that there is nothing that the user must do. > What about mingw64 packages? > > Previously I think we have just been happy that packages built okay under the > default mechanism, and only used cmake with make or ninja, depending on which > worked to give the desired package(s). > Usually, I also check the same package available from MSYS2, to be sure that it is at least at the same level. I hope that this could be useful. Sincerely, Carlo Bramini.
