1. replace apt-get with new apt
2. install all in one command
Can we use this from travis: https://docs.travis-ci.com/user/installing-dependencies/#adding-apt-packages
Why? It is in its own compilation unit anyways. Is there a way this can be visible somewhere else? I use anonymous namespaces only for files that will be included, but I do not know best practices for this
Why? It is in its own compilation unit anyways. Is there a way this can be visible somewhere else? I use anonymous namespaces only for files that will be included, but I do not know best practices for this
neuron303
(Migrated from github.com)
reviewed 2019-09-23 21:49:14 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
LGTM :P
Travis fails but just does not support C++14 .. lets fix that later :D
totally not talking to myself
Can we use this from travis: https://docs.travis-ci.com/user/installing-dependencies/#adding-apt-packages
@@ -15,0 +17,4 @@OsciWidget::OsciWidget(QWidget *parent): QOpenGLWidget{parent}, m_bufferOffset{m_buffer.begin()}, m_lastBufferUpdate{0}anonymous namespace?
@@ -15,0 +17,4 @@OsciWidget::OsciWidget(QWidget *parent): QOpenGLWidget{parent}, m_bufferOffset{m_buffer.begin()}, m_lastBufferUpdate{0}Why? It is in its own compilation unit anyways. Is there a way this can be visible somewhere else? I use anonymous namespaces only for files that will be included, but I do not know best practices for this
@@ -15,0 +17,4 @@OsciWidget::OsciWidget(QWidget *parent): QOpenGLWidget{parent}, m_bufferOffset{m_buffer.begin()}, m_lastBufferUpdate{0}Well you are right of course .. you could link against it if you reuse the name :)