FvwmConsole from meson build is missing?

Other things FVWM Installation
1

hi all,

fvwm3 is migrating towards using meson as its build system. from the latest git checkout (hash: 1067a72e) i don’t see ‘FvwmConsole’ module being built.

here are the steps that i have followed:

1. meson setup \
--prefix=$HOME/local/usr \
--buildtype=release optimized-build \
-Dc_args="-march=native -mtune=native -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer" \
-Dmandoc=true \
-Dhtmldoc=true

2. meson compile -C optimized-build

3. cd optimized-build

4. find ./ -name 'FvwmConsole' | wc
 0       0       0

step-4 returns nothing :o)

quite sure that i might have missed something fundamental. can the experts here please help ?

canonical build from autotools seems to do the right thing though.

–
thank you
kind regards

2

replying to myself:

a trivial hack does seem to do the trick, however i am not so sure if the omission was deliberate ?

would taking this up at github be the ‘right-thing’ to do ?

–
thank you
kind regards

3

FvwmPrompt has replaced FvwmConsole. The logic is if you have golang installed, FvwmPrompt will be built instead of FvwmConsole. If you don’t have golang installed, FvwmConsole is built instead. You can explicitly disable golang with -Dgolang=disabled in your setup.

I would suggest just moving to and learning FvwmPrompt. The only real difference is you don’t launch it from fvwm, instead just open up any terminal and run FvwmPrompt as a binary, and it gives you a shell you can send fvwm commands. You can also just use FvwmPrompt <fvwmcommand> if you want to send a single command with out opening up the shell.

Note you will need to load FvwmMFL using Module FvwmMFL from your StartFunction, since that is what FvwmPrompt uses to communicate with fvwm.

4

Note, just to clarify the above, in autotools, golang was disabled by default and has to be explicitly enabled, in meson, golang is automatically detected and builds FvwmPrompt if it is detected, so has to be explicitly disabled in that case.

5

FvwmPrompt has replaced FvwmConsole. The logic is if you have golang installed, FvwmPrompt will be built instead of FvwmConsole. If you don’t have golang installed, FvwmConsole is built instead. You can explicitly disable golang with -Dgolang=disabled in your setup.

yes that is exactly right ! thank you ! fwiw, after sending that message yesterday, i looked around a bit, and stumbled across the modules dictionary in the build file, and then the golang <---> FvwmConsole dependency right after that.

so that mystery got fixed.

however, i had no idea about FvwmPrompt, so thank you once again for clearing that up too ! as you have suggested, i have updated my configuration to load FvwmMFL during startup (specifically, during Init) and start a FvwmPrompt instance (within urxvt) as and when requested.

regarding your comment

Note, just to clarify the above, in autotools, golang was disabled by default and has to be explicitly enabled, in meson, golang is automatically detected and builds FvwmPrompt if it is detected, so has to be explicitly disabled in that case.

once again you are right. i typically don’t build fvwm with golang support, and your explanation clears this up too !

–
thank you
kind regards