Sponsored Content
Top Forums Programming Need help changing a makefile to static linking Post 303031202 by ACorner on Saturday 23rd of February 2019 12:47:35 PM
Old 02-23-2019
Need help changing a makefile to static linking

Hi all,

I'm having a hard time compiling a plugin (softhddevice) for the video disk recorder software (vdr). Unfortunately the last official version of the plugin was published back in 2013 and even worse it has to be compiled against ffmpeg. The last working version of ffmpeg was 2.8.x, patches should make it work with 3.5.x (if you can find them). It's definitely not working with ffmpeg 4.x
So my thought was to forget about all the trouble with different versions and compile the plugin against a static built and working version of ffmpeg.
That was the quickly found plan, but the implementation is more than difficult if you are not used to deal with makefiles.
I tried to copy parts of the makefile(s) of tvheadend (which btw does exactly what I have in mind) that simply adds the .a files to the linking command. But without success. I know that there's the possibility to tell pck-config to use static libraries, but I have no glue where exactly in the makefile I have to insert this command and how I can force pkg-config to search within the ffmpeg directory.
I hope someone can push me in the right direction.
Thanks in advance
Alex
 

9 More Discussions You Might Find Interesting

1. Programming

Linking problem while linking to shared library

Hi I'm getting ld: fatal: option -h and building a dynamic executable are incompatible ld: fatal: Flags processing errors When I run ld -shared -L/usr/dt/lib -lDtSvc -o builtin.so Workspace.o after running gcc -fPIC -I/usr/X11R6/include -I/usr/dt/include -c Workspace.c I'm... (6 Replies)
Discussion started by: laho
6 Replies

2. Programming

differeEEK!nce between static and dynamic linking

hello, friends i would like to know what is the differnce between static library and dynamic library? How will u create them and what are there uses? (1 Reply)
Discussion started by: vijaya2006
1 Replies

3. Programming

dynamic linking of folder name in makefile

i will tell my problem with example: if i have a folder name called sree1.7.3 i know the starting name say sree and also path say /usr/lib. so i want the folder name. and how can i link this folder in makefile thank u sree (1 Reply)
Discussion started by: phani_sree
1 Replies

4. HP-UX

HP-UX 10.xx Changing from static IP to DHCP

***Newbie alert*** What's the easiest way to accomplish this? An admin left our company and I have taken over his HP Workstation and moved it to a different location that is on a different IP segment. I have performed a number of google searches but the steps I have followed haven't worked. ... (1 Reply)
Discussion started by: Steelysteel
1 Replies

5. Shell Programming and Scripting

How to change a Makefile from building static library to shared library?

Hi: I have a library that it only offers Makefile for building static library. It built libxxx.a file. How do I in any way build a shared library? (either changin the Makefile or direct script or command to build shared library) Thanks. (1 Reply)
Discussion started by: cpthk
1 Replies

6. IP Networking

I need HELP to Set up Coyote Linux router with 1 static IP & 64 internal static IP

hello, i need help on setting my coyote linux, i've working on this for last 5 days, can't get it to work. I've been posting this message to coyote forum, and other linux forum, but haven't get any answer yet. Hope someone here can help me...... please see my attached picture first. ... (0 Replies)
Discussion started by: dlwoaud
0 Replies

7. Programming

Adding a Static Library (libtimer.a) to the Makefile

Hi, The following is my Makefile, I wanted to add a staic library named libtimer.a. I'm using the following Makefile. Please let me know how to add this static library: Makefile:- It produces "usbserial" executable. Thanks, S (1 Reply)
Discussion started by: suryaemlinux
1 Replies

8. Programming

Static and Shared Library in Makefile

I am having a devil of a time with a very simple make file. The program needs two shared and one static library. If I link the shared libraries only like below the mysql test app works ... (1 Reply)
Discussion started by: jadsys
1 Replies

9. Shell Programming and Scripting

Help understanding makefile: static pattern rules

Hi all, I'm reading the GNU Make book I cannot understand the following syntax from the book. objects = foo.o bar.o all : $(objects) $(objects) : %.o : %.c $(CC) -c $(CFLAGS) $< -o $@ If I run: make, I get the output: cc -c foo.c cc -o foo foo.o I think I... (3 Replies)
Discussion started by: santiagorf
3 Replies
Jifty::Plugin(3pm)					User Contributed Perl Documentation					Jifty::Plugin(3pm)

NAME
Jifty::Plugin - Describes a plugin to the Jifty framework DESCRIPTION
Plugins are like mini-apps. They come in packages with share directories which provide static and template files; they provide actions; they have dispatcher rules. To create the skeleton of a new plugin, you can use the command: jifty plugin --name SomePlugin To use a plugin in your Jifty application, find the "Plugins:" line in the "config.yml" file: Plugins: - SpiffyThing: {} - SomePlugin: arguments: to the: constructor The dispatcher for a plugin should live in "Jifty::Plugin::name::Dispatcher"; it is written like any other Jifty::Dispatcher. Plugin dispatcher rules are checked before the application's rules; however, see "Plugins and rule ordering" in Jifty::Dispatcher for how to manually specify exceptions to this. Actions and models under a plugin's namespace are automatically discovered and made available to applications. new Sets up a new instance of this plugin. This is called by Jifty after reading the configuration file, and is supplied whatever plugin- specific settings were in the config file. Note that because plugins affect Mason's component roots, adding plugins during runtime is not supported. init [ARGS] Called by "new", this does any custom configuration that the plugin might need. It is passed the same parameters as "new", gleaned from the configuration file. new_request Called right before every request. By default, does nothing. template_root Returns the root of the "HTML::Mason" template directory for this plugin po_root Returns the plugin's message catalog directory. Returns undef if it doesn't exist. template_class Returns the Template::Declare view package for this plugin static_root Returns the root of the static directory for this plugin dispatcher Returns the classname of the dispatcher class for this plugin prereq_plugins Returns an array of plugin module names that this plugin depends on. version Returns the database version of the plugin. Needs to be bumped any time the database schema needs to be updated. Plugins that do not directly define any models don't need to worry about this. bootstrapper Returns the name of the class that can be used to bootstrap the database models. This normally returns the plugin's class name with "::Bootstrap" added to the end. Plugin bootstrappers can be built in exactly the same way as application bootstraps. See Jifty::Bootstrap. upgrade_class Returns the name of the class that can be used to upgrade the database models and schema (such as adding new data, fixing default values, and renaming columns). This normally returns the plugin's class name with "::Upgrade" added to the end. Plugin upgrade classes can be built in exactly the same was as application upgrade classes. See Jifty::Upgrade. table_prefix Returns a prefix that will be placed in the front of all table names for plugin models. Be default, the plugin name is converted to an identifier based upon the class name. wrap Takes a PSGI-$app closure and returns the wrapped one if your plugin wants to do something to the request handling process. See also Plack::Middleware. psgi_app_static Returns a PSGI-$app that serves the static content of the plugin if any. The default is a <Plack::App::File> app with root set to plugin's "static_root" perl v5.14.2 2010-12-08 Jifty::Plugin(3pm)
All times are GMT -4. The time now is 12:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy