Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC: Building from source

Building from source 3 years 1 month ago #10959

  • davew
  • davew's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 16
  • Karma: 0
I'm trying to build from the source tar ball available from sourceforge.

The overall process seems to complete but there is a worrying error generated.

Exporting rt_videomgm.h
Exporting rt_xtt_main.h
Exporting rt_xtt_cmd.h
In file included from /tmp/xtt_i_methods.c:1:
/home/pwrp/proview_build_root/os_linux/hw_x86_64/exp/inc/xtt_menu.h:40:10: fatal error: pwr_class.h: No such file or directory
 #include "pwr_class.h"
          ^~~~~~~~~~~~~
compilation terminated.
ar: creating /home/pwrp/proview_build_root/os_linux/hw_x86_64/exp/lib/libpwr_xtt.a
ar: /tmp/xtt_i_methods.o: No such file or directory
rm: cannot remove '/tmp/xtt_i_methods.o': No such file or directory
Set flavour qt
-- Build module rt
Exporting op_macros.h
Exporting op_resources.h


I expect this will cause problems at run time.

Can anyone help?
The administrator has disabled public write access.

Building from source 3 years 1 month ago #10961

  • claes
  • claes's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 3178
  • Thank you received: 502
  • Karma: 133
It seem to be a minor error in merging of modules, but this is done several times later in the build process, so it will probably not affect the final result.

/Claes
The administrator has disabled public write access.
The following user(s) said Thank You: davew

Building from source 3 years 1 month ago #10962

  • davew
  • davew's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 16
  • Karma: 0
I see.
Actually your reply prompted me to check the compile log and I see libpwr_xtt.a is built several times during the process.

I tried to fix the error but I'm having real difficulty understanding the build process. Specifically, for the moment, what controls export of files for a module build.

This build process seems extremely convoluted and I would like to understand it fully with a view to creating aditional I/O modules. I assume the build process is complicated because of the many different envionments and OSs it supports.

Also, is there something in the build process that will trigger building debian packages like the official distribution packages on sourceforge?
The administrator has disabled public write access.

Building from source 3 years 1 month ago #10965

  • claes
  • claes's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 3178
  • Thank you received: 502
  • Karma: 133
Command to build the debian packages is

pwre build tools/pkg deb_x86_64 src

/Claes
The administrator has disabled public write access.
The following user(s) said Thank You: davew

Building from source 3 years 1 month ago #10966

  • davew
  • davew's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 16
  • Karma: 0
Claes,
Thank you so much for the assistance.

I have progressed forwards and built new debian packages which appear to support libnodave.

I now have a new problem. There is nothing in the Ge palette to place on graphics.

I began with a clean slate since I had properly messed up the environment.
I built a new machine to host the source code so its a clean latest debian.

I configured my build environament as

--
-- Environment    : V571NDx86_64
-- Module.........:
-- Source root....: /home/davew/projects/pwrsrc_5.7.1-1/src
-- Build root.....: /home/davew/projects/pwr_build_dbg
-- Build type.....: dbg
-- OS.............: linux
-- Hardware.......: x86_64
-- Description....: Nodave debug build
--
himBHs

pwre configure shows
...Checking         /bin/bash
Mandatory :
...Checking   Yes   librpcsvc
...Checking   Yes   libasound
...Checking   Yes   libpthread
...Checking   Yes   libm
...Checking   Yes   libdb
...Checking   Yes   libdb_cxx
...Checking   Yes   libz
...Checking   Yes   libcrypt
...Checking   Yes   librt
...Checking   Yes   libX11
...Checking   Yes   alsa

Gui either Qt or Gtk :
...Checking   Yes   qt
...Checking   Yes   qt
...Checking   Yes   qt
...Checking   Yes   qt
...Checking   Yes   qt
...Checking   Yes   gtk
...Checking   Yes   gtk

Optional :
...Checking   No    jni
...Checking   No    jni
...Checking   No    motif
...Checking   Yes   mysql
...Checking   Yes   sqlite3
...Checking   Yes   libsqlite3
...Checking   Yes   hdf5
...Checking   Yes   hdf5
...Checking   Yes   libhdf5
...Checking   Yes   libhdf5
...Checking   Yes   rabbitmq
...Checking   No    mq
...Checking   No    wmq
...Checking   No    libprofinet
...Checking   Yes   libusb
...Checking   No    powerlink
...Checking   No    powerlinkcn
...Checking   Yes   libpcap
...Checking   Yes   librsvg
...Checking   Yes   gst
...Checking   Yes   gst
...Checking   No    mq
...Checking   No    wmq
...Checking   No    cifx
...Checking   Yes   nodave
...Checking   No    powerlink
...Checking   No    powerlinkuser
...Checking   Yes   rsvg
...Checking   Yes   pydev
...Checking   No    android
himBHs

Then I followed the process to build_all_modules.

After build_all_modules I built the deb packages using the command you provided.

Then I built another clean debian machine to host the dev environment and installed the pwr57_5.7.1-1_amd64.deb built from my source tree.

I then created a test project as per the getting started guide except I created a more simplified PLC programme with only 3 DV objects.

I then created a graphic and linked it the fast access.

Everything worked absolutely fine until I tried to edit the graphic when I discovered the palette contains no widgets.

Have I missed something somewhere?
The administrator has disabled public write access.

Building from source 3 years 1 month ago #10967

  • davew
  • davew's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 16
  • Karma: 0
Sorry.
I found the answer to this in another topic.
I'll read more of that before asking agin.
The administrator has disabled public write access.
  • Page:
  • 1
Time to create page: 8.751 seconds