OLD | NEW |
1 ###################################### | 1 ###################################### |
2 Dynamic Linking and Loading with glibc | 2 Dynamic Linking and Loading with glibc |
3 ###################################### | 3 ###################################### |
4 | 4 |
5 .. contents:: | 5 .. contents:: |
6 :local: | 6 :local: |
7 :backlinks: none | 7 :backlinks: none |
8 :depth: 2 | 8 :depth: 2 |
9 | 9 |
10 Introduction | 10 Introduction |
(...skipping 289 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
300 As an alternative to using ``create_nmf``, it is possible to manually calculate | 300 As an alternative to using ``create_nmf``, it is possible to manually calculate |
301 the list of shared library dependencies using tools such as ``objdump_``. | 301 the list of shared library dependencies using tools such as ``objdump_``. |
302 | 302 |
303 Deploying a dynamically linked application | 303 Deploying a dynamically linked application |
304 ========================================== | 304 ========================================== |
305 | 305 |
306 As described above, an application's manifest file must explicitly list all the | 306 As described above, an application's manifest file must explicitly list all the |
307 executable code modules that the application directly depends on, including | 307 executable code modules that the application directly depends on, including |
308 modules from the application itself (.nexe and .so files), modules from the | 308 modules from the application itself (.nexe and .so files), modules from the |
309 Native Client SDK (e.g., libppapi_cpp.so), and perhaps also modules from | 309 Native Client SDK (e.g., libppapi_cpp.so), and perhaps also modules from |
310 `naclport <naclports_>`_ or from :doc:`middleware systems <../../community/middl
eware>` that | 310 `naclport <naclports_>`_ or from `middleware systems <../../community/middleware
>`_ that |
311 the application uses. You must provide all of those modules as part of the | 311 the application uses. You must provide all of those modules as part of the |
312 application deployment process. | 312 application deployment process. |
313 | 313 |
314 As explained in :doc:`Distributing Your Application | 314 As explained in :doc:`Distributing Your Application |
315 <../distributing>`, there are two basic ways to deploy an application: | 315 <../distributing>`, there are two basic ways to deploy an application: |
316 | 316 |
317 * **hosted application:** all modules are hosted together on a web server of | 317 * **hosted application:** all modules are hosted together on a web server of |
318 your choice | 318 your choice |
319 | 319 |
320 * **packaged application:** all modules are packaged into one file, hosted in | 320 * **packaged application:** all modules are packaged into one file, hosted in |
(...skipping 102 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
423 **undefined reference to 'dlopen' collect2: ld returned 1 exit status** | 423 **undefined reference to 'dlopen' collect2: ld returned 1 exit status** |
424 This is a linker ordering problem that usually results from improper ordering | 424 This is a linker ordering problem that usually results from improper ordering |
425 of command line flags when linking. Reconfigure your command line string to | 425 of command line flags when linking. Reconfigure your command line string to |
426 list libraries after the -o flag. | 426 list libraries after the -o flag. |
427 | 427 |
428 .. |menu-icon| image:: /images/menu-icon.png | 428 .. |menu-icon| image:: /images/menu-icon.png |
429 .. _objdump: http://en.wikipedia.org/wiki/Objdump | 429 .. _objdump: http://en.wikipedia.org/wiki/Objdump |
430 .. _GLIBC: http://www.gnu.org/software/libc/index.html | 430 .. _GLIBC: http://www.gnu.org/software/libc/index.html |
431 .. _POSIX: http://en.wikipedia.org/wiki/POSIX | 431 .. _POSIX: http://en.wikipedia.org/wiki/POSIX |
432 .. _newlib: http://sourceware.org/newlib/ | 432 .. _newlib: http://sourceware.org/newlib/ |
OLD | NEW |