|
From: Rui N. C. <rn...@rn...> - 2022-03-01 18:02:16
|
hi every1, for quite some time I've been noticing that windows builds are failing (see subject) probably due to old autoconf/automake build system being dropped in favor to now official cmake... and one other thing: the front-page/web is no longer reflecting the *svn updates, ever since this late Mon Nov 22 17:08:21 CET 2021, as it seems... is there anything I can do to help? thanks && cheers -- rncbc aka. Rui Nuno Capela rn...@rn... |
|
From: Christian S. <sch...@li...> - 2022-03-01 19:15:59
|
On Dienstag, 1. März 2022 19:01:53 CET Rui Nuno Capela wrote: > hi every1, Hi Rui, > for quite some time I've been noticing that windows builds are failing > (see subject) probably due to old autoconf/automake build system being > dropped in favor to now official cmake... > > and one other thing: the front-page/web is no longer reflecting the *svn > updates, ever since this late Mon Nov 22 17:08:21 CET 2021, as it seems... > > is there anything I can do to help? As for the build errors: if you find some time, try to login to the CI page and change the compilatation commands accordingly. cmake is already installed. Otherwise I will have some time at the weekend to handle it. As for the frontsite: I don't think there is any issue. You were not commiting with star "*" in front. That's why it did not show up there (expected behaviour since 2003). Best regards, Christian Schoenebeck |
|
From: Rui N. C. <rn...@rn...> - 2022-03-01 22:45:55
|
On 3/1/22 18:33, Christian Schoenebeck wrote: > On Dienstag, 1. März 2022 19:01:53 CET Rui Nuno Capela wrote: > > As for the frontsite: I don't think there is any issue. You were not commiting > with star "*" in front. That's why it did not show up there (expected > behaviour since 2003). > hi Christian oops, you're right, this one missed the asterisk: -- r4023 | capela | 2022-01-09 10:45:21 +0000 (Sun, 09 Jan 2022) | 1 line 0.9.5 -- exactly the same with liblscp a few minutes earlier: -- r4022 | capela | 2022-01-09 10:43:35 +0000 (Sun, 09 Jan 2022) | 1 line 0.9.5 -- it should have been '* A Winter'22 Release (v0.9.5)" but somehow only the "0.9.5" got through, maybe my fault :( thanks anyway -- rncbc aka. Rui Nuno Capela rn...@rn... |
|
From: Christian S. <sch...@li...> - 2022-03-02 16:03:40
|
On Dienstag, 1. März 2022 23:45:30 CET Rui Nuno Capela via Linuxsampler-devel wrote: > On 3/1/22 18:33, Christian Schoenebeck wrote: > > On Dienstag, 1. März 2022 19:01:53 CET Rui Nuno Capela wrote: > > > > As for the frontsite: I don't think there is any issue. You were not > > commiting with star "*" in front. That's why it did not show up there > > (expected behaviour since 2003). > > hi Christian > > oops, you're right, this one missed the asterisk: > -- > r4023 | capela | 2022-01-09 10:45:21 +0000 (Sun, 09 Jan 2022) | 1 line > > 0.9.5 > -- > > exactly the same with liblscp a few minutes earlier: > -- > r4022 | capela | 2022-01-09 10:43:35 +0000 (Sun, 09 Jan 2022) | 1 line > > 0.9.5 > -- > > it should have been '* A Winter'22 Release (v0.9.5)" but somehow only > the "0.9.5" got through, maybe my fault :( > > thanks anyway NP. :) BTW git style comments are accepted by the server side scripts as well, i.e.: " one-line summary of this commit * Some detailed explanation. * And another detailed one. " or " one-line summary of this commit * Some detailed explanation. * And another detailed one. " E.g.: http://svn.linuxsampler.org/cgi-bin/viewvc.cgi?view=revision&revision=3804 As long as at least one line starts with an asterisk character somewhere, then the commit log is published on the front site. If another form would be more intuitive for you, we can still extend the scripts of course. Best regards, Christian Schoenebeck |
|
From: Christian S. <sch...@li...> - 2022-03-05 09:40:51
|
On Dienstag, 1. März 2022 19:33:31 CET Christian Schoenebeck wrote: > On Dienstag, 1. März 2022 19:01:53 CET Rui Nuno Capela wrote: > > hi every1, > > Hi Rui, > > > for quite some time I've been noticing that windows builds are failing > > (see subject) probably due to old autoconf/automake build system being > > dropped in favor to now official cmake... > > > > and one other thing: the front-page/web is no longer reflecting the *svn > > updates, ever since this late Mon Nov 22 17:08:21 CET 2021, as it seems... > > > > is there anything I can do to help? > > As for the build errors: if you find some time, try to login to the CI page > and change the compilatation commands accordingly. cmake is already > installed. Otherwise I will have some time at the weekend to handle it. I fear the current requirement is too high: CMake 3.15 or higher is required. You are running version 3.13.4 Rui, please check if you can lower the cmake version requirement. If it is not possible then I fear I have to leave this broken for months to come, as I don't have time to update the server for this right now. Sorry. Best regards, Christian Schoenebeck |
|
From: Rui N. C. <rn...@rn...> - 2022-03-05 17:02:48
|
On 3/5/22 09:40, Christian Schoenebeck wrote: > On Dienstag, 1. März 2022 19:33:31 CET Christian Schoenebeck wrote: >> On Dienstag, 1. März 2022 19:01:53 CET Rui Nuno Capela wrote: >>> hi every1, >> >> Hi Rui, >> >>> for quite some time I've been noticing that windows builds are failing >>> (see subject) probably due to old autoconf/automake build system being >>> dropped in favor to now official cmake... >>> >>> and one other thing: the front-page/web is no longer reflecting the *svn >>> updates, ever since this late Mon Nov 22 17:08:21 CET 2021, as it seems... >>> >>> is there anything I can do to help? >> >> As for the build errors: if you find some time, try to login to the CI page >> and change the compilatation commands accordingly. cmake is already >> installed. Otherwise I will have some time at the weekend to handle it. > > I fear the current requirement is too high: > > CMake 3.15 or higher is required. You are running version 3.13.4 > > Rui, please check if you can lower the cmake version requirement. If it is not > possible then I fear I have to leave this broken for months to come, as I > don't have time to update the server for this right now. Sorry. > hi Christian, what you mean? this is what: cmake_minimum_required (VERSION 3.13) cmake 3.15 is actually only required if you follow the build instructions on the homepage: cmake -B build && cmake --build build && cmake --install build but may try the older way instead: cmake -B build && make -C build && make -C build install or even older: mkdir build cd build cmake .. && make && make install hth. cheers -- rncbc aka. Rui Nuno Capela rn...@rn... |
|
From: Christian S. <sch...@li...> - 2022-03-05 17:57:08
|
On Samstag, 5. März 2022 18:02:22 CET Rui Nuno Capela via Linuxsampler-devel wrote: > On 3/5/22 09:40, Christian Schoenebeck wrote: > > On Dienstag, 1. März 2022 19:33:31 CET Christian Schoenebeck wrote: > >> On Dienstag, 1. März 2022 19:01:53 CET Rui Nuno Capela wrote: > >>> hi every1, > >> > >> Hi Rui, > >> > >>> for quite some time I've been noticing that windows builds are failing > >>> (see subject) probably due to old autoconf/automake build system being > >>> dropped in favor to now official cmake... > >>> > >>> and one other thing: the front-page/web is no longer reflecting the *svn > >>> updates, ever since this late Mon Nov 22 17:08:21 CET 2021, as it > >>> seems... > >>> > >>> is there anything I can do to help? > >> > >> As for the build errors: if you find some time, try to login to the CI > >> page > >> and change the compilatation commands accordingly. cmake is already > >> installed. Otherwise I will have some time at the weekend to handle it. > > > > I fear the current requirement is too high: > > CMake 3.15 or higher is required. You are running version 3.13.4 > > > > Rui, please check if you can lower the cmake version requirement. If it is > > not possible then I fear I have to leave this broken for months to come, > > as I don't have time to update the server for this right now. Sorry. > > hi Christian, > > what you mean? this is what: > > cmake_minimum_required (VERSION 3.13) OK, I see that you just lowered this to 3.13. Thanks! The api-doc-lscp job is working now again. I look for the other CI targets tommorow. As we are cross compiling I have to figure out what the equivalent with cmake is. Previously we had, e.g.: ["liblscp-win32" target]: ./configure --host=i686-w64-mingw32 --prefix=$install_dir --disable-static make -j4 make install-strip ["liblscp-mac-x86_64" target]: CC="clang -target x86_64-apple-darwin11 -B $toolchain/cctools/bin --sysroot=$toolchain/MacOSX10.7.sdk" \ CXX="clang++ -target x86_64-apple-darwin11 -B $toolchain/cctools/bin --sysroot=$sdk/MacOSX10.7.sdk" \ CXXFLAGS="-stdlib=libc++ -std=c++11 -I/usr/include/c++/v1 -O2 -ffast-math -fomit-frame-pointer" \ ./configure --host=x86_64-apple-darwin11 --disable-static --prefix=$install_dir make -j4 make install-strip If you already have some idea about the equivalents, let me know. You can also just login to the build page and try yourself in the meantime if you want. Best regards, Christian Schoenebeck |
|
From: Rui N. C. <rn...@rn...> - 2022-03-06 11:33:34
|
On 3/5/22 17:56, Christian Schoenebeck wrote: > On Samstag, 5. März 2022 18:02:22 CET Rui Nuno Capela via Linuxsampler-devel wrote: >> On 3/5/22 09:40, Christian Schoenebeck wrote: >>> On Dienstag, 1. März 2022 19:33:31 CET Christian Schoenebeck wrote: >>>> On Dienstag, 1. März 2022 19:01:53 CET Rui Nuno Capela wrote: >>>>> hi every1, >>>> >>>> Hi Rui, >>>> >>>>> for quite some time I've been noticing that windows builds are failing >>>>> (see subject) probably due to old autoconf/automake build system being >>>>> dropped in favor to now official cmake... >>>>> >>>>> and one other thing: the front-page/web is no longer reflecting the *svn >>>>> updates, ever since this late Mon Nov 22 17:08:21 CET 2021, as it >>>>> seems... >>>>> >>>>> is there anything I can do to help? >>>> >>>> As for the build errors: if you find some time, try to login to the CI >>>> page >>>> and change the compilatation commands accordingly. cmake is already >>>> installed. Otherwise I will have some time at the weekend to handle it. >>> >>> I fear the current requirement is too high: >>> CMake 3.15 or higher is required. You are running version 3.13.4 >>> >>> Rui, please check if you can lower the cmake version requirement. If it is >>> not possible then I fear I have to leave this broken for months to come, >>> as I don't have time to update the server for this right now. Sorry. >> >> hi Christian, >> >> what you mean? this is what: >> >> cmake_minimum_required (VERSION 3.13) > > OK, I see that you just lowered this to 3.13. Thanks! > The api-doc-lscp job is working now again. > > I look for the other CI targets tommorow. As we are cross compiling I have to > figure out what the equivalent with cmake is. Previously we had, e.g.: > > ["liblscp-win32" target]: > ./configure --host=i686-w64-mingw32 --prefix=$install_dir --disable-static > make -j4 > make install-strip > > ["liblscp-mac-x86_64" target]: > CC="clang -target x86_64-apple-darwin11 -B $toolchain/cctools/bin --sysroot=$toolchain/MacOSX10.7.sdk" \ > CXX="clang++ -target x86_64-apple-darwin11 -B $toolchain/cctools/bin --sysroot=$sdk/MacOSX10.7.sdk" \ > CXXFLAGS="-stdlib=libc++ -std=c++11 -I/usr/include/c++/v1 -O2 -ffast-math -fomit-frame-pointer" \ > ./configure --host=x86_64-apple-darwin11 --disable-static --prefix=$install_dir > make -j4 > make install-strip > > If you already have some idea about the equivalents, let me know. You can also > just login to the build page and try yourself in the meantime if you want. > hi Christian, no idea, never tried cross-compilation with cmake, but this would be a start: https://cmake.org/cmake/help/book/mastering-cmake/chapter/Cross%20Compiling%20With%20CMake.html# thanks -- rncbc aka. Rui Nuno Capela rn...@rn... |