Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #104849

Re: How to produce standalone executable using Code::Blocks/Clang ?

Show all headers | View raw

On Mon, 27 Feb 2017 12:14:12 +0000
BartC <bc@freeuk.com> wrote:

> What's the difference between dynamic linking and dynamic loading 
> according to you?

For example a call to dlopen() by the programmer in the latter case.

 
> To me, they both describe what happens at load-time and run-time, long 
> after the compiler and linker have done their jobs.

Dynamic linking imply the use of a dynamic linker at run-tine which load
and link the library only at start-up by the initiative of the system.

Dynamic loading can be see as a special case of dynamic linking but the loading
process is initiated by the programmer.


> I wouldn't break it down further, except that perhaps loading better 
> describes the one-time loading of the whole shared library the first 
> time is is needed, and linking might describe the fix-up needed of an 
> individual function.

For me it's cystal clear that loading is more relevant to describe the
programmer action on the linking process.


> Some months ago the disk caching used by Firefox on one of my machines 
> had somehow grown without restraints for the best part of a year. It had 
> used up some 150GB; not the entire drive, but a big chunk of it.
> 
> Deleting the 3 million files generated took 17 HOURS.
> 
> Some people seem to think that because storage is so cheap as to be 
> practically free, that using it comes without any costs.

Bad programmers do bad things such as disk cache or swap file. What else?


> My C:/windows directory contains 20,000 .dll files totalling some 14GB. 
> Only 1.4% of a 1TB drive, but it would obviously be chaotic if all the 
> hundreds of applications that used those dlls decided to statically link 
> them in.

Programmers couldn't blame the system vendor for providing bad code.


> A program using features of an OS doesn't need to contain the entire OS 
> within itself.
> 
> They are called /shared/ libraries for a good reason.

As I said you only save space to waste time with shared libraries. Nobody is
forced to use broken system libraries... because the end product is under the
responsiblity of the programmer.

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

How to produce standalone executable using Code::Blocks/Clang ? MehdiAmini <atorrses@gmail.com> - 2017-02-26 12:01 +0330
  Re: How to produce standalone executable using Code::Blocks/Clang ? fir <profesor.fir@gmail.com> - 2017-02-26 01:55 -0800
    Re: How to produce standalone executable using Code::Blocks/Clang ? fir <profesor.fir@gmail.com> - 2017-02-26 03:35 -0800
  Re: How to produce standalone executable using Code::Blocks/Clang ? David Brown <david.brown@hesbynett.no> - 2017-02-26 14:40 +0100
    Re: How to produce standalone executable using Code::Blocks/Clang ? BartC <bc@freeuk.com> - 2017-02-26 14:13 +0000
      Re: How to produce standalone executable using Code::Blocks/Clang ? David Brown <david.brown@hesbynett.no> - 2017-02-26 17:26 +0100
        Re: How to produce standalone executable using Code::Blocks/Clang ? BartC <bc@freeuk.com> - 2017-02-26 16:56 +0000
          Re: How to produce standalone executable using Code::Blocks/Clang ? David Brown <david.brown@hesbynett.no> - 2017-02-26 19:00 +0100
            Re: How to produce standalone executable using Code::Blocks/Clang ? scott@slp53.sl.home (Scott Lurndal) - 2017-02-27 15:16 +0000
        Re: How to produce standalone executable using Code::Blocks/Clang ? scott@slp53.sl.home (Scott Lurndal) - 2017-02-27 15:12 +0000
          Re: How to produce standalone executable using Code::Blocks/Clang ? David Brown <david.brown@hesbynett.no> - 2017-02-27 16:43 +0100
    Re: How to produce standalone executable using Code::Blocks/Clang ? GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-02-27 01:12 +0100
      Re: How to produce standalone executable using Code::Blocks/Clang ? BartC <bc@freeuk.com> - 2017-02-27 01:04 +0000
        Re: How to produce standalone executable using Code::Blocks/Clang ? GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-02-27 06:05 +0100
          Re: How to produce standalone executable using Code::Blocks/Clang ? David Brown <david.brown@hesbynett.no> - 2017-02-27 10:27 +0100
            Re: How to produce standalone executable using Code::Blocks/Clang ? GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-02-27 12:21 +0100
              Re: How to produce standalone executable using Code::Blocks/Clang ? BartC <bc@freeuk.com> - 2017-02-27 12:14 +0000
                Re: How to produce standalone executable using Code::Blocks/Clang ? GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-02-27 14:27 +0100
              Re: How to produce standalone executable using Code::Blocks/Clang ? David Brown <david.brown@hesbynett.no> - 2017-02-27 13:55 +0100
      Re: How to produce standalone executable using Code::Blocks/Clang ? Ike Naar <ike@iceland.freeshell.org> - 2017-02-27 08:26 +0000
        Re: How to produce standalone executable using Code::Blocks/Clang ? GOTHIER Nathan <nathan.gothier@gmail.com> - 2017-02-27 12:25 +0100
          Re: How to produce standalone executable using Code::Blocks/Clang ? Ike Naar <ike@iceland.freeshell.org> - 2017-02-27 15:24 +0000
      Re: How to produce standalone executable using Code::Blocks/Clang ? David Brown <david.brown@hesbynett.no> - 2017-02-27 10:22 +0100
      Re: How to produce standalone executable using Code::Blocks/Clang ? scott@slp53.sl.home (Scott Lurndal) - 2017-02-27 15:20 +0000
        Re: How to produce standalone executable using Code::Blocks/Clang ? fir <profesor.fir@gmail.com> - 2017-02-27 07:45 -0800
          Re: How to produce standalone executable using Code::Blocks/Clang ? fir <profesor.fir@gmail.com> - 2017-02-27 08:12 -0800
    Re: How to produce standalone executable using Code::Blocks/Clang ? MehdiAmini <atorrses@gmail.com> - 2017-02-27 10:54 +0330

csiph-web