Welcome!
Forum users

Current releases
--MX-23 release info here
--Migration information to MX-23 here
--antiX-23.1 (Arditi del Popolo) release info here

Important information
--If in starting your system it boots to an unwanted Desktop, right click desktop, then select leave and logout. At the
login screen there is a session chooser at the top of the screen.

News
-- MX Linux on social media: here
-- New Forum Features, Marking Solved and Referencing a User: here

Problem with libstdc

Message
Author
User avatar
timkb4cq
Developer
Posts: 3179
Joined: Wed Jul 12, 2006 4:05 pm

Re: Problem with libstdc

#11 Post by timkb4cq »

Praat is written in C and C++ in a fairly modular fashion. There are over 1300 source files in over 30 directories (not including the 900+ declaration files) that are compiled and linked into the 3 binary executable files.

But as Stevo said, we don't really have to worry about that in any detail. The authors include a Makefile that does most of the work. The debian packaging does some setup, lists the dependencies for the apt/aptitude/Synaptic package managers & handles installation into the correct directories & menus.

Rebuilding a correctly formed package on our library set is often just installing build dependencies, updating the changelog, and running the build program. Sometimes dependencies that aren't available yet in our repos have to be built first.

It's when the program won't compile with our libraries that we have to dig into the code. We aren't expert programmers, but there are some things we can track down & fix by investigating the error messages - and then there are the ones you don't see because we can't.
HP Pavillion TP01, AMD Ryzen 3 5300G (quad core), Crucial 500GB SSD, Toshiba 6TB 7200rpm
Dell Inspiron 15, AMD Ryzen 7 2700u (quad core). Sabrent 500GB nvme, Seagate 1TB

User avatar
radissthor
Posts: 67
Joined: Mon Sep 13, 2010 11:18 am

Re: Problem with libstdc

#12 Post by radissthor »

timkb4cq wrote:Praat is written in C and C++ in a fairly modular fashion. There are over 1300 source files in over 30 directories (not including the 900+ declaration files) that are compiled and linked into the 3 binary executable files.

But as Stevo said, we don't really have to worry about that in any detail. The authors include a Makefile that does most of the work. The debian packaging does some setup, lists the dependencies for the apt/aptitude/Synaptic package managers & handles installation into the correct directories & menus.

Rebuilding a correctly formed package on our library set is often just installing build dependencies, updating the changelog, and running the build program. Sometimes dependencies that aren't available yet in our repos have to be built first.

It's when the program won't compile with our libraries that we have to dig into the code. We aren't expert programmers, but there are some things we can track down & fix by investigating the error messages - and then there are the ones you don't see because we can't.
Many thanks to all the packagers and the people in general that make this mepis/MX project available for everyone. In my 5 and something years using Mepis and MX I never stop learning from you guys :worship:
Image

Post Reply

Return to “General”