Re: [MSEide-MSEgui-talk] msei18n vs PO files

2019-05-06 Thread fredvs
> Now, this leaves the question where to put this compiler switch. If it 
> was be needed for all targets, it might be best to put it into some 
> ressource string yet to be defined. If it is not needed always, or 
> perhaps on Linux only, it might be acceptable to put it into the compiler 
>specification field in the settings dialog. 

Those switches are needed for Unix but ignored with Windows.
If I remember ok, with fp 2.6.4 it was not needed.

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk


Re: [MSEide-MSEgui-talk] msei18n vs PO files

2019-05-06 Thread fredvs
> Now I DID clean up the mess from previous failed attempts before trying the
recompile, and it DID work. 

Nice that it works now!
Yes, it is because a **very** old fpc bug.
Even using "-B" (build all) fpc does not clean all previous compiled files.
One of the cause is because fpc forget the included files {$I
something.inc}.

> Now, this leaves the question where to put this compiler switch.

If you use the graphic msei18n application (/mseide-msegui/tools/msei18n/),
click on the "Edit" menu-button.
By default, the needed parameters are added.

Could you give the script that you are using for compiling?

Fre;D



--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk


Re: [MSEide-MSEgui-talk] msei18n vs PO files

2019-05-06 Thread Sieghard
Hello fredvs,

following up my previous post about the error compiling the "language"
libraries, I found the cause now. The clue & key was the compiler's
suggestion "recompile with -fPIC"
Well I had tried that before, and it hadn't helped. But this might have
been due to my not cleaning up the working directory beforehand, so the
compiler didn't really recompile, just retry the link step - and failed
again.
Now I DID clean up the mess from previous failed attempts before trying
the recompile, and it DID work.
Now, this leaves the question where to put this compiler switch. If it
was be needed for all targets, it might be best to put it into some
ressource string yet to be defined. If it is not needed always, or
perhaps on Linux only, it might be acceptable to put it into the compiler
specification field in the settings dialog.
Which again leaves the question: What do you (& other list members) think?

-- 
-- 
(Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung
nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem)
---
Mit freundlichen Grüßen, S. Schicktanz
---




___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk


Re: [MSEide-MSEgui-talk] msei18n vs PO files

2019-05-06 Thread fredvs
> It seems this version was meant to already use "mselang" compilatiin or at 
> least compilation via llvm that it was meant to use, but as the regular 
> What are you (& other list members) thinking? 

I think there is a confusion, there is no call (yet) to mselang (the
compiler).

There is indeed a call to /mseide-msegui/lib/common/i18n/mselanglink.pas but
it has nothing to do with mselang-compiler.
This unit is about registering mse-languages.

Fre;D




--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk


Re: [MSEide-MSEgui-talk] msei18n vs PO files

2019-05-06 Thread fredvs
Hello Sieghard.

Thanks to give attention to msegui.

> calling "Make" for a project I set up, "msei18n.trp", returns this error: 

Are you trying to compile on a Unix machine (Linux or FreeBSD) ?

If yes, you should add "-fPIC" parameter to fpc compiler option:

I use this macro with the gui msei18n :
/mseide-msegui/tools/i18n/msei18n.prj :

${COMPILER} -Fu${MSELIBDIR}i18n ${LIBFILE} -fPIC -k-gc-sections

Note the 2 last parameters: -fPIC (needed for compilation) and
-k-gc-sections (to enable garbage collector).

Also dont forget do remove all previous *.ppu, *.o, ... etc.

Fre;D
 








--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/


___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk


Re: [MSEide-MSEgui-talk] msei18n vs PO files

2019-05-06 Thread Sieghard
Hello fredvs,

by the way, I got the latest msei18n programs to compile and run now, both
the one from release 4.6.2 and from your gitlab repository.
But they don't work correctly. Apart from an error shown on calling:
"Sessionmanager Error: SESSION_MANAGER environment variable not defined"
(that I didn't investigate yet, as it seems to run normally otherwise)
calling "Make" for a project I set up, "msei18n.trp", returns this error:
-
"/mnt/ext/Linux/install/Entwicklung/fpc/MSE-IDE/MSE-IDE.4_6_2/tools/i18n/i18n.latest.script/de/".
Free Pascal Compiler version 3.0.2 [2018/05/11] for x86_64 Copyright (c)
1993-2017 by Florian Klaempfl and others Target OS: Linux for x86-64
Compiling msei18n_de.pas
Compiling project_mfm.pas
Compiling empty_rst.pas
Linking ./libmsei18n_de.so
/usr/bin/ld: warning: ./link.res contains output sections; \
did you forget -T?
/usr/bin/ld: mselanglink.o: relocation R_X86_64_32S against symbol \
`U_$MSELANGLINK_$$_REGISTERMODULEHOOK' can not be used when making \
a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: \
nonrepresentable section on output
msei18n_de.pas(8) Error: Error while linking
msei18n_de.pas(8) Fatal: There were 1 errors compiling module, \
stopping
Fatal: Compilation aborted Exec error 1. ERROR 
-
(Lines with a "\" at the end continued on next line.)
It seems this version was meant to already use "mselang" compilatiin or at
least compilation via llvm that it was meant to use, but as the regular
setup still uses fpc, this won't work. Asusing fpc MIGHT still be the
normal case, it might be warranted to change that (back) to allow fpc to be
used.
What are you (& other list members) thinking?

-- 
-- 
(Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung
nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem)
---
Mit freundlichen Grüßen, S. Schicktanz
---




___
mseide-msegui-talk mailing list
mseide-msegui-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk