#shared library

I'd say grab a cycle of five commanders so that people aren't left with access to nothing when their opponent casts the commander. Each player can't cast commanders while they already have one, so with five of them, everybody should keep at least some choice of what they get. (of course, you have to send it back when it leaves the battlefield and doesn't return at a set time.)

They would have to be generic enough to play well with the same deck not optimized for any of them. Likely spanning all five colors.

New Post has been published on http://www.learn-digital-marketing.com/ranking-the-adwords-shared-library-features/

Ranking The AdWords Shared Library Features

The AdWords Shared Library isn’t the sexiest feature, but it does provide valuable options that can make account management more efficient.

I spent 2 hours debugging last night and another 2 hours today to find the reason for random crashes at application exit.

When using Allegro 5 in a shared library, it is very important to use al_uninstall_system() manually (I guess allegro can't call this in atexit() in those cases for some reason).

5 Steps to make a shared library and use it

1. Compile your code [Remember to add the Position Independent Flag -fPIC]

    gcc -fPIC -c simple.c -o simple.o

2. Create a Shared Library

    gcc -shared -Wl,-soname,libsimple.so.1 -o libsimple.so.1.0 simple.o

3. Create the Symbolic Links [This step is necessary only if you add the version to the -o libsimple.so.1.0. You specify libsimple.so, in that case this step is not necessary ]

   ln -s libsimple.so.1 libsimple.so

4. Process the Folder for shared library. +foldername+ is the path where you placed the shared library.

   ldconfig -n <foldername>

5. If the library is in non standard path then set LD_LIBRARY_PATH

   In Bash: export LD_LIBRARY_PATH=.:$LD_LIBRARY_PATH

  Now you can use your shared library [compile your code & Run].

   gcc -o test test.c -L. -lsimple