|
Re: How to create service for FORTE using Windows [message #1858353 is a reply to message #1858348] |
Thu, 30 March 2023 06:34 |
|
AFIK nobody has done something like this sofar.
What I would recommend is to provide a second main in a separate file and utilize some of our startup shutdown infrastructure (e.g., similar to what we are doing for freeRTOS or RCx) to implement the functionality. Then you could add a cmake switch that allows to switch between the classic main and your new one.
|
|
|
|
|
|
Re: How to create service for FORTE using Windows [message #1865043 is a reply to message #1858348] |
Thu, 25 April 2024 07:42 |
Ketut Kumajaya Messages: 26 Registered: January 2024 |
Junior Member |
|
|
More alternative solution: https://github.com/winsw/winsw
Example config for forte:
<!--
MIT License
Copyright (c) 2008-2020 Kohsuke Kawaguchi, Sun Microsystems, Inc., CloudBees,
Inc., Oleg Nenashev and other contributors
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
-->
<!--
This is an example of a minimal Windows Service Wrapper configuration, which includes only mandatory options.
This configuration file should be placed near the WinSW executable, the name should be the same.
E.g. for myapp.exe the configuration file name should be myapp.xml
You can find more information about the configuration options here: https://github.com/kohsuke/winsw/blob/master/doc/xmlConfigFile.md
Full example: https://github.com/kohsuke/winsw/blob/master/examples/sample-allOptions.xml
-->
<service>
<!-- ID of the service. It should be unique across the Windows system-->
<id>forte_service</id>
<!-- Display name of the service -->
<name>FORTE Service</name>
<!-- Service description -->
<description>This service is 4diac FORTE service</description>
<!-- Path to the executable, which should be started -->
<executable>forte.exe</executable>
<!--
OPTION: workingdirectory
If specified, sets the default working directory of the executable.
Default value: Directory of the service wrapper executable.
-->
<workingdirectory>C:\msys64\home\user\forte\install\amd64\bin</workingdirectory>
<!--
OPTION: arguments
Arguments, which should be passed to the executable.
-->
<arguments>-mc configMqtt.forte -oc configSecurity.forte</arguments>
</service>
|
|
|
Powered by
FUDForum. Page generated in 0.42546 seconds