They’re not exactly screensavers , just fullscreen apps.
the mouse and startbar show up when they are running , you have to set startbar properties to “Allow windows to cover”
So i’ve got some questions:
how to make an rpm package?
how to make a screensaver?
where do screensavers go on the filesystem? , so the rpm can put the files in the right place.
On Mon, 03 Apr 2017 16:16:01 +0000, Albert Redditt wrote:
> How exactly , do you make an rpm package from your software?
> Is there a tutorial somewhere?
>
> I wrote two OpenGL screen savers called “Morphius” , solid and wireframe
> versions.
> I’d like to put them into an rpm package…’
>
> https://sourceforge.net/projects/mor...es/Linux%2064/’
> (http://tinyurl.com/lvse7km)
>
>
> They’re not exactly screensavers , just fullscreen apps.
> the mouse and startbar show up when they are running , you have to set
> startbar properties to “Allow windows to cover”
>
> So i’ve got some questions:
> 1) how to make an rpm package?
> 2) how to make a screensaver?
> 3) where do screensavers go on the filesystem? , so the rpm can put the
> files in the right place.
You install the rpm-build package , but the executable is called “rpmbuild” and not “rpm-build” like the package name, couldn’t find rpm-build (took awhile to figure it out.)
The tutorial is for making an auto-make source package, that self builds the program and installs it…and it’s quite dated , for SUSE 11.3
I just want to package two executables into a package…Not sure how to do it ?
But before i can make a package , i,ve got to learn the X11 stuff , for properly making a real , bonafide screensaver.
My Morphius apps work under Windows , you just give them a “scr” extension and stick it in the system32 folder and it shows up in the screensavers section.
On Linux it’s just a full screen , borderless app. and the mouse and startbar show up for some reason?
On Mon 03 Apr 2017 07:56:02 PM CDT, Albert Redditt wrote:
You should be able to just do something simple , like:
rpmbuild -make_package [package_name] binary1 , binary2 , lib1 , lib2
, [docs] , spec-file what dirs to put apps and libs in ]
With Linux though, there’s always tons of switches to every app. and
most console apps , are real hard to use.
Hi
If you want to use OBS, then you need to compile from source, no binary
blobs… please. Else my recommendation to anyone seeing this is
don’t go blindly download and install a binary blob. What license is
this released under?
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.38-50-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
On Mon, 03 Apr 2017 18:26:01 +0000, Albert Redditt wrote:
> I found an rpm build tutorial.
>
> http://tinyurl.com/m5uy9cw
>
> You install the rpm-build package , but the executable is called
> “rpmbuild” and not “rpm-build” like the package name, couldn’t find
> rpm-build (took awhile to figure it out.)
> The tutorial is for making an auto-make source package, that self builds
> the program and installs it…and it’s quite dated , for SUSE 11.3
>
> I just want to package two executables into a package…Not sure how to
> do it ?
I’d start with reading the spec file format and learn that.
> But before i can make a package , i,ve got to learn the X11 stuff , for
> properly making a real , bonafide screensaver.
> My Morphius apps work under Windows , you just give them a “scr”
> extension and stick it in the system32 folder and it shows up in the
> screensavers section.
>
> On Linux it’s just a full screen , borderless app. and the mouse and
> startbar show up for some reason?
That’s a separate development question that’s better for the development
forum.
The problem is , I’m using FreeBASIC 64 Linux to compile.
So there’s no ./configure , make , make install
The program is just a single *.bas file.
And FreeBASIC compiles to *.exe by default to the dir that the program is in.
I could set FB to output C files or ASM files and put those into the SOURCE dir? ( But FB outputs , really ugly looking C code )
And i’m not sure if it would include the libs code , in the ASM or C code. (I’d have to ask on the FB forum.)
By default FB includes the lib code in the end executable (called static linking ) with “as” assembler and “ld” linker.
So the only thing i can think of is to put precompiled binaries into the package , which ain’t allowed. So i’m stuck!!!
I’ll ask on the FB Linux forum if anyone has ever had experience with making packages…
