New release of JWM (Joe Window Manager)

[fredvs]

JWM is not Linux specific anymore, it is also not bloated like other window managers. There is an interest in it for FreeBSD, or especially desktop variants.

I suggest trying LLVM/Clang to compile it. I don't see much responsibility for FreeBSD to troubleshoot GCC (because even if successful, it will go right back to using ambiguous coding, for its mission), except where people want to to make programs that require it work. If there is a major problem for GCC, that fixing it will benefit many operating systems, the developers of that program will do it, because it fixes it for their choice OS.

Hello sidetone and thanks for your excellent advice.
Of course I am open to use LLVM vs GCC.
And JWM is a perfect example.

Could you, please, give the step-by-step way (like I did for GCC) to compile JWM GitHub-source with LLVM37 ?

Many thanks.

Fre;D

 

[sidetone]

For all of the ports, it's in /etc/make.conf, to choose which compiler and version. It's probably in the handbook. It should use the compiler that's existing with your system.

To go by Gitfile, use the porter's handbook. https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ . The same subject is repeated with one part giving better detail. Copy the port's Makefile of JWM, to its own custom directory to examine and edit it. I don't see automake or autoconf in it's Makefile. First remove the existing JWM package before compiling.

Which features are you trying to activate? Because the latest version of JWM in ports is the new version 2.3.6. You can ask the maintainer to include an option for what you're trying to use, after you've tested it.

* edit - its in the port's Makefile to choose which complier and version to use for individual ports.

 

[DutchDaemon]

Gentlemen (fredvs, marino@), there's nothing wrong with a lively debate, but can we stop short of the inside boundary of civility? Thanks.

 

[fredvs]

I don't see automake or autoconf in it's Makefile.

They are in the " autogen.sh" script and are needed to create the Makefile and configure scripts.

Which features are you trying to activate? Because the latest version of JWM in ports is the new version 2.3.6. You can ask the maintainer to include an option for what you're trying to use, after you've tested it.

Take a look at https://github.com/joewing/jwm
There are new commits and Joe is busy to make JWM voice-asssistable.
I will be one of his tester.

Please, I do not want to depend of the pkg maintainer to have the permission to compile original source.


Fre;D

 

[fredvs]

Gentlemen (fredvs, marino@), there's nothing wrong with a lively debate, but can we stop short of the inside boundary of civility? Thanks.

I think that I stay polite, but when somebody ask to not answer to my questions and that I have to stay in my "little world", it is aggressive.

Fre;D

 

[sidetone]

Read my last post again. You can copy jwm's Makefile from ports to a custom folder, edit it, and compile it, after removing the jwm package.

Once you compile and test it on your own, you can inform the maintainer what works.

The Porters Handbook and other existing FreeBSD documentation should give some pointers for compiling on your own.

 

[fredvs]

Read my last post again. You can copy jwm's Makefile from ports to a custom folder, edit it, and compile it, after removing the jwm package.

Once you compile and test it on your own, you can inform the maintainer what works.

The Porters Handbook and other existing FreeBSD documentation should give some pointers for compiling on your own.

Thanks sidetone.

But I will tell you all.

I already tried to compile JWM original code with LLVM37 ( with ./configure CC=LLVM37 CXX=LLVM37 )
Compilation failed because "error in syntax" (because not 100% compatible C code) . And then the original code must be changed.

But, ok, I will take a look at the Makefile from ports. If it is only the Makefile that must be changed, ok.

Fre;D