Hi all,
first, thanks Chris for bringing this up.
I also wanted to start this discussion on the list but thank you very much for
doing it and the nice writeup.
We now have 4 languages (Java, C++, C# and Python) and hopefully more to come
(C would be really nice, I personally think and as some o
Hey everyone,
I would also opt for Maven being at least the triggering build system because
it also integrates well with Jenkins and the mechanisms behind it are quite
understandable.
I think the main point we need to solve is to get some kind of documentation
which build step in which profile
+1 hybrid system
Matthias Strljic, M.Sc.
Universität Stuttgart
Institut für Steuerungstechnik der Werkzeugmaschinen und
Fertigungseinrichtungen (ISW)
Seidenstraße 36
70174 Stuttgart
GERMANY
Tel: +49 711 685-84530
Fax: +49 711 685-74530
E-Mail: matthias.strl...@isw.uni-stuttgart.de
Web: http:/
+1 for the Maven Hybrid solution
(CoC, Ease of use [something I miss when I work with other languages], solving
occurring problems)
Sebastian
> Am 27.05.2019 um 14:41 schrieb Christofer Dutz :
>
> Hi all,
>
> as the discussion had come up multiple times now … mainly on Slack, I would
> like
Hello everybody,
it's always a problem to get different pholosphies under one hat.
On the part of C++, CMake is not only available in Visual Studio, but also for
other platforms.
On the CMake side, different parameters can be specified for the build process.
In the end, Maven could calculate
BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [373]':
Is back to normal.
Hi all,
as the discussion had come up multiple times now … mainly on Slack, I would
like to do a dedicated discussion here on the list about the topic.
Up to now we had built the build to generally build every module with maven,
utilizing plugins to enable triggering builds with things like CMa
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [374]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/374/";>PLC4X/PLC4X/develop
[develop] [374]"
BUILD-STABLE: Job 'PLC4X/PLC4X/develop [develop] [371]':
Is back to normal.
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [372]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/372/";>PLC4X/PLC4X/develop
[develop] [372]"
Hi Markus,
It claims that this is missing ... however it isn't missing ...
The files are all there and are all where they should be. That's what's
puzzling me.
Chris
Am 27.05.19, 11:58 schrieb "Markus Sommer" :
Hello, Chris,
in the module Logger the header file boost\system\err
For fairness few last builds (369, 370) were caused by my faulty commit
which got merged. Sorry about that.
Best,
Łukasz
On 27.05.2019 11:46, Christofer Dutz wrote:
> Hi all,
>
> as I had to enable the compilation in the logger module in order to reliably
> produce the error with the build, th
Hello, Chris,
in the module Logger the header file boost\system\error_code.hpp is missing, in
the directory target/dependencies.
I'll take a look at the Maven topic at this point.
Best regards
Markus
Freundliche Grüße
Markus Sommer
Geschäftsführer
isb innovative software businesses GmbH
Ot
Hello Chris,
I'd like to wait for Björn's feedback. He also has this problem.
To include, if I put the header files into a directory, that doesn't mean I
include all files from that directory. If I use any header files, I see the
includes of the header or source file of the object.
You see the
Hi all,
as I had to enable the compilation in the logger module in order to reliably
produce the error with the build, this broke the build, as expected … so until
the C++ build I fixed, we’ll not build it on Jenkins.
I’ll create a feature-branch “feature/cpp-build” … there it’s enabled again.
But if you do this, it's sort of an
#include
There is no way to control which dependencies a module sees and needs.
It would result in every module referencing every dependency any module needs
to add to the pool.
Chris
Am 27.05.19, 11:18 schrieb "Markus Sommer" :
Hello, Chris,
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [370]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/370/";>PLC4X/PLC4X/develop
[develop] [370]"
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [369]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/369/";>PLC4X/PLC4X/develop
[develop] [369]"
Hello, Chris,
you generate a target/dependencies folders for each module (api, logger,
driver-base, etc.).
I mean, we generate a target/dependencies at the plc4cpp level and combine all
libs and includes of the plc4cpp modules and external modules like Boost.
Each individual module would then
Łukasz Dywicki created PLC4X-129:
Summary: Version detection macro fails with releases in x.y format
Key: PLC4X-129
URL: https://issues.apache.org/jira/browse/PLC4X-129
Project: Apache PLC4X
BUILD-FAILURE: Job 'PLC4X/PLC4X/develop [develop] [368]':
Check console output at "https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/368/";>PLC4X/PLC4X/develop
[develop] [368]"
Hi Markus,
I would be able to help, if you stop by in Frankfurt ... but I would prefer to
discuss anything we would be thinking about here on the list.
Ideally meeting won't be necessary in the end as we sorted all the problems.
Isn't that what I'm currently doing in the build? It automatically
So,
I just checked the changes ... and the build does not work correctly.
But I left the compilation enabled and we will have breaking builds until this
is fixed.
The error message is:
[INFO] --- cmake-maven-plugin:3.7.2-b1:compile (cmake-compile) @
plc4cpp-utils-logger ---
Scanning depende
Hello, Chris,
we can meet in Frankfurt, when I get back to the north.
If we see each module ourselves, we would also have to copy the libs and header
files from the individual plc4cpp modules to the others.
What do you think about not doing these dependencies for each module, but
simply seeing
Hi Markus,
I did talk to you about this in our last session. And it once worked while we
did it in Stuttgart.
You introduced the problems by dropping code you didn't test with our primary
build system, which is Maven.
And it's not really a fun trip for me to travel to Stuttgart cause it takes m
Hello, Chris,
I looked at the pom.xml on the weekend. To resolve the dependencies towards
Boost, a local duplicate is created in the Dependencies folder. The duplicate
is then created for each module.
To include Boost in CMake you can use the following in the top level:
set(BOOST_ROOT "./libs/
The Apache PLC4X team is pleased to announce the release of Apache PLC4X 0.4.0
PLC4X is a set of libraries for communicating with industrial programmable
logic controllers (PLCs) using a variety of protocols but with a shared API.
The current release contains drivers able to communicate with
indu
27 matches
Mail list logo