. git clone git://anongit.kde.org/libmm-qt
. mkdir libmm-qt_build
. cd libmm-qt_build
. cmake -DCMAKE_INSTALL_PREFIX=/usr ../libmm-qt
. make && make install
. git clone git://anongit.kde.org/libnm-qt
. mkdir libnm-qt_build
. cd ../libnm-qt_build
. cmake -DCMAKE_INSTALL_PREFIX=/usr ../libnm-qt
. make && make install
Compiling master branch is still the same:
. git clone git://anongit.kde.org/networkmanagement
. mkdir networkmanagement_build
. cd networkmanagement_build
. cmake -DCMAKE_INSTALL_PREFIX=/usr ../networkmanagement
. make && make install
I must say this new Plasma NM + libnm-qt is working quite good, no big problems in the last days. I will start to port the usability changes to master branch early next month, for now there are other things that require my attention.
. mkdir libmm-qt_build
. cd libmm-qt_build
. cmake -DCMAKE_INSTALL_PREFIX=/usr ../libmm-qt
. make && make install
. git clone git://anongit.kde.org/libnm-qt
. mkdir libnm-qt_build
. cd ../libnm-qt_build
. cmake -DCMAKE_INSTALL_PREFIX=/usr ../libnm-qt
. make && make install
Compiling master branch is still the same:
. git clone git://anongit.kde.org/networkmanagement
. mkdir networkmanagement_build
. cd networkmanagement_build
. cmake -DCMAKE_INSTALL_PREFIX=/usr ../networkmanagement
. make && make install
I must say this new Plasma NM + libnm-qt is working quite good, no big problems in the last days. I will start to port the usability changes to master branch early next month, for now there are other things that require my attention.
6 comments:
can you describe the benefits to having three separate repositories?
now i have three times the work to do to keep up with kde networkmanagement and three times as much to explain to people starting fresh.
is there at least a kdesrc-build module configuration for this?
libnm-qt and libmm-qt are completely non-related from API point of view and in the future they are going to move to NetworkManager and ModemManager's repositories, which are also separated. I wanted to keep the logs separated and that was the only option I could find. They are not in networkmanagement reopository because of the same reason and because that would force anybody to install Plasma NM to have them installed.
There is no benefit for KDE users in having three repositories, it is just a convinience for when the libraries leave projects.kde.org. But both libraries are small and should have very few commits from now on. Once distributions start to pack it there should be very few upgrades, so this problem can be minimized.
Hi,
I've tried to compile all that this morning and at the end of networkmanagement I obtain the following error :
/home/michal/SOFTWARE/PLASMA-NM/networkmanagement/vpnplugins/openconnect/openconnectauthworkerthread.cpp: In constructor ‘OpenconnectAuthWorkerThread::OpenconnectAuthWorkerThread(QMutex*, QWaitCondition*, bool*)’:
/home/michal/SOFTWARE/PLASMA-NM/networkmanagement/vpnplugins/openconnect/openconnectauthworkerthread.cpp:81:46: error: ‘openconnect_vpninfo_new_with_cbdata’ was not declared in this scope
Any hint ? (I'm on Debian testing/unstable).
Thanks, Michal
@Michal, that function is declared in openconnect.h. Which openconnect version do you have installed? I use 3.11 and it compiles Ok here.
Hi,
I'm using openconnect 3.02, this explains the problem.
I've another question : my wifi configuration gets lost between sessions. I must delete it and recreate in order to get the connection otherwise it tries to connect and waits for authentication indefinitely.
Thanks again,
Michal
@Michal, the minimum required is 3.03. I will add a warning for when the minimum required is not installed. It is a warning not error because openconnect is optional.
Post a Comment