Build Forte error [message #1730941] |
Sat, 30 April 2016 09:21 |
emanuele vitolo Messages: 4 Registered: April 2016 |
Junior Member |
|
|
Hi all, i'm new in this forum, i have a problem with 4DIAC.
Speciically, when i make deployment with Forte with Pre-Existent Functional Blocks everything work, but when i create new functional blocks....forte recognize only the OLD pre-existent FB!
This is hoy i did:
- i create a new functional block
- exported its .cpp and .f files in the Forte\src\modules\utils
- added the line in the cmakelist.txt in the utils folder
- opened cmake, configured using the root forte directory as source code, Forte\bin\win32 as destination folder, using visual studio 8 2009 as generator and using the native compiler,checked FORTE_ARCHITECTURE_WIN32, FORTE_MODULE_CONVERT, FORTE_MODULE_IEC61131, FORTE_MODULE_TEST, FORTE_MOODULE_UTILS, FORTE_SUPPORT_MONITORING, pressed again configure since red flags don't appaer, pressed generate button
- opened visual studio generated solution with visual studio 2008
- setted release mode
- build forte......AND HERE THE PROBLEM!
"Errore 45 fatal error C1083: Impossibile aprire il file inclusione 'E_CYCLE_gen.cpp': No such file or directory"
PLEASE....HELP ME :\
|
|
|
|
|
|
|
|
Re: Build Forte error [message #1750603 is a reply to message #1750579] |
Fri, 23 December 2016 08:29 |
|
Hi,
when doing cross compiling you also need a crosscompiled libmodbus. In such cases most of the time a normal install of the libmodbus is not sufficient. There is a flag which allows you to give the also the directory where you crosscompiled your libmodbus.
|
|
|
|
Re: Build Forte error [message #1751302 is a reply to message #1750791] |
Sat, 07 January 2017 10:39 |
|
Hi,
comlayersmanger.cpp is a file that is generated by cmake during the configurationprocess. It should not be necessary to that you manually need to change it. It seams that there is a error in the setup of cmake. I currently have no good test environment for modbus. Therefore I kindly ask if you could add the following line:
forte_add_include_directories(${CMAKE_CURRENT_SOURCE_DIR})
into the CMakeLists.txt file in the modules/modbus directory and see if it fixes the issue?
Thank,
Alois
|
|
|
Re: Build Forte error [message #1755882 is a reply to message #1751302] |
Wed, 08 March 2017 22:00 |
joseph reveane Messages: 13 Registered: March 2016 |
Junior Member |
|
|
Hi,
I've tried to build Forte 1.8.4 code base with Modbus RTU (for getting access to RS485 devices) on a x86 platform with Debian 8 installed using Cmake but I get the following errors during the compilation:
home/jreveane/4Diac/Bundle/FORTE_1.8.4/src/modules/modbus/modbusconnection.cpp: In member function 'virtual int CModbusConnection::connect()':
/home/jreveane/4Diac/Bundle/FORTE_1.8.4/src/modules/modbus/modbusconnection.cpp:35:64: error: invalid conversion from 'timeval*' to 'uint32_t {aka unsigned int}' [-fpermissive]
modbus_set_response_timeout(m_pModbusConn, &responseTimeout);
^
/home/jreveane/4Diac/Bundle/FORTE_1.8.4/src/modules/modbus/modbusconnection.cpp:35:64: error: too few arguments to function 'int modbus_set_response_timeout(modbus_t*, uint32_t, uint32_t)'
In file included from /home/jreveane/4Diac/Bundle/FORTE_1.8.4/src/modules/modbus/modbusconnection.h:22:0,
from /home/jreveane/4Diac/Bundle/FORTE_1.8.4/src/modules/modbus/modbusconnection.cpp:11:
/home/jreveane/4Diac/Bundle/build/modbus.h:186:16: note: declared here
MODBUS_API int modbus_set_response_timeout(modbus_t *ctx, uint32_t to_sec, uint32_t to_usec);
^
/home/jreveane/4Diac/Bundle/FORTE_1.8.4/src/modules/modbus/modbusconnection.cpp:41:56: error: invalid conversion from 'timeval*' to 'uint32_t {aka unsigned int}' [-fpermissive]
modbus_set_byte_timeout(m_pModbusConn, &byteTimeout);
^
/home/jreveane/4Diac/Bundle/FORTE_1.8.4/src/modules/modbus/modbusconnection.cpp:41:56: error: too few arguments to function 'int modbus_set_byte_timeout(modbus_t*, uint32_t, uint32_t)'
In file included from /home/jreveane/4Diac/Bundle/FORTE_1.8.4/src/modules/modbus/modbusconnection.h:22:0,
from /home/jreveane/4Diac/Bundle/FORTE_1.8.4/src/modules/modbus/modbusconnection.cpp:11:
/home/jreveane/4Diac/Bundle/build/modbus.h:189:16: note: declared here
MODBUS_API int modbus_set_byte_timeout(modbus_t *ctx, uint32_t to_sec, uint32_t to_usec);
^
src/CMakeFiles/forte.dir/build.make:1710: recipe for target 'src/CMakeFiles/forte.dir/modules/modbus/modbusconnection.cpp.o' failed
make[2]: *** [src/CMakeFiles/forte.dir/modules/modbus/modbusconnection.cpp.o] Error 1
CMakeFiles/Makefile2:125: recipe for target 'src/CMakeFiles/forte.dir/all' failed
make[1]: *** [src/CMakeFiles/forte.dir/all] Error 2
Makefile:117: recipe for target 'all' failed
I had a look at the Forte build documentation for Unix platform and the Modbus page as well but this didn't really help.
So, is there any HowTo which would explain the Forte Build on Linux with Modbus RTU support ?
Thanks in advance for your help.
Regards.
|
|
|
|
|
|
Re: Build Forte error [message #1794272 is a reply to message #1794239] |
Tue, 28 August 2018 11:24 |
|
Typically libmodbus.so will just be a symbolic link. In your case I assume it points to libmodbus.so.5. So you the question would be if you installed libmodbus in your system. Then something with the install process seems to be broken. If you just build your own libmodbus. Then you need also the files where all the symbolic so links are pointing to in the directory of forte executable.
|
|
|
Powered by
FUDForum. Page generated in 0.05380 seconds