Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Problem with libstdc

Message
Author
User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 4416
Joined: Wed Jul 12, 2006 4:05 pm

Re: Problem with libstdc

#11 Post by timkb4cq » Tue Nov 17, 2015 8:45 pm

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.
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

User avatar
radissthor
Forum Regular
Forum Regular
Posts: 342
Joined: Mon Sep 13, 2010 11:18 am

Re: Problem with libstdc

#12 Post by radissthor » Wed Nov 18, 2015 9:23 am

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”