| Re: [4diac-dev] Providing RPMs for 4DIAC Forte |
Hi,just a quick answer to your last question which seams for now for me the most important part. All OPC UA development is already in the development branch and also maintained and further developed there. The problem is that as commiter I'm currently not allowed to delete/close feature branches. I hope I can sort this out soon.Cheers,AloisGesendet: Montag, 04. September 2017 um 18:10 Uhr
Von: "Jens Reimann" <jreimann@xxxxxxxxxx>
An: "4diac developer discussions" <4diac-dev@xxxxxxxxxxx>
Betreff: Re: [4diac-dev] Providing RPMs for 4DIAC ForteJensCheersThanks for your helpI would like to continue adding OPC UA support as a next step, because this is my actual interest ;) Is there any chance to see the OPC_UA branch merged soon? Or should I continue working on a branch for that?You can then also drop in the git repository into "copr" [1], and let copr do a CI build, much like Travis does it, but only for RPMs.This works fine in local setup. Bringing forte to a Raspberry Pi is rather painless and involves no cross-compiling that way.Two allows to do a local RPM build by executing "tito build --test --rpm", or "tito build --test --srpm". This will use the content of the local git repository with the last commit (so local modifications won't be present in the build). The --rpm option will build locally. The --srpm option only creates a source RPM which can then be build e.g. on a Raspberry Pi with "rpmbuild --rebuild src.rpm". It will also apply the git commit ref to the version, indicating a snapshot build.I did come up with a relatively painless way of building an RPM out of forte: https://git.eclipse.org/r/#/c/Hi Alois,this is great to hear. I am currently working on getting open62541 into Fedora. Currently this looks good, the review is accepted and maybe forte could also become a port of Fedora in the future. Doing a simple 'dnf install 4diac-forte" to install forte would be great ;-)
104294/
______________________________On Sun, Sep 3, 2017 at 8:49 PM, Alois Z. <alois.zoitl@xxxxxx> wrote:Hi Jens,
until recently I would have said that it is not so interesting for 4diac. The main reason would have been that a typical 4diac users would need to compile its own FORTE with her own Fbs anyhow. However a few things happened which changed my mind a bit. First of all in an internal project we noticed how cumbersome it is to build your FORTE for different platforms, deploy it and start it. Especially in a cross compilation scenario with different compilers and target operating systems. There my colleagues are experimenting with Docker images and Gitlab CI. I haven’t seen results yet but I can keep you updated.
The second thing is that with the first version of integrating Lua into FORTE the need for recompiling FORTE is gone. This increases the need for providing standard prebuilt FORTEs for different platforms.
Therefore I think the answer is yes even if I currently don’t know how it impacts us.
Regarding your question 2 I must confess that I don’t know enough about rpm packages to give here an answer. The only thing that I can see is that in addition to source directories also the Cmake configuration should be adjustable. Don’t know if parameters can be given to a spec file.
And finally to your question 3: FORTE does not distinguish the startups. Normally in the default configuration FORTE looks on start-up if it finds in the directory it was started from (or a location specified in an environment variable) a boot file. If it finds one it tries to load it if not this step is ignored. Even if a boot-file is loaded a user can connect with the ide and remove the loaded content from a FORTE. The only thing that is currently not possible is that you connect your ide to a running forte and explore what is currently running inside. BTW this could be a nice goog le summer or code project for next year.
As now more and more PLCs and PLC like devices are migrating to Linux having such a systemd unit could greatly simplify the deployment of FORTEs.
Alois
Gesendet: Freitag, 01. September 2017 um 16:34 Uhr
Von: "Jens Reimann" <jreimann@xxxxxxxxxx>
An: "4diac developer discussions" <4diac-dev@xxxxxxxxxxx>
Betreff: [4diac-dev] Providing RPMs for 4DIAC Forte______________________________JensCheersPlease let me know what you think.3) Currently forte is not being started. My proposal would be to create a systemd unit for starting this as a system service. From what I remember there are two ways to start forte. a) with a "boot file" and b) empty, deploying the application over the remote socket. Bot ways make sense in different scenarios to me. a) is probably more for production, while b) is more for development. So there could be two systemd unit to reflect that. One could probably start automatic when the boot file is present (copied over by some).2) Currently the "spec" file can only be used for CI builds, for a release build it would need to be adopted manually in order to point to a correct source location. I have no good idea here, but I am open for suggestions.1) Would the project be interested in adopting this? I am happy to help, but if there is no interest I think it isn't any good.Right now I am building integration builds using "copr" [1], and also for open62541 [2]. as my goal would be to have forte with OPC UA support. The current state is available on GitHub in a fork I created [3].Hi,I was playing a bit around, creating RPMs of Forte for Fedora. My goal would be to provide a rather simple way of dropping forte into a Fedora machine.
My primary motivation is to get a simple, reproducible setup on a Raspberry Pi with Forte. I already did this 2 times and every time started from scratch as I forgot the different steps. I think some "out-of-the-box" experience would help, at least me ;)The following topics are still unsolved and I would like to get your feedback on that:
[1] https://copr.fedorainfracloud.org/coprs/ctron/4diac-forte/
[2] https://copr.fedorainfracloud.org/coprs/ctron/open62541/
[3] https://github.com/ctron/org.eclipse.4diac.forte/
--Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
____________________________________________________________ _________________
Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill_________________ 4diac-dev mailing list 4diac-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/ mailman/listinfo/4diac-dev
_______________________________________________
4diac-dev mailing list
4diac-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/4diac-dev
--Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
____________________________________________________________ _________________
Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill_________________ 4diac-dev mailing list 4diac-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/ mailman/listinfo/4diac-dev
_______________________________________________
4diac-dev mailing list
4diac-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/4diac-dev