splee wrote:Where can i find the source code for the command line tool, so that I could check all the return codes?
You asked for it!!!
The command 'main()' function is in "utilities/convert.c" Though in IMv7 that is being obsoleted for "utilities/magick.c".
This module is however simple a call to a 'wrapper' library function MagickCommandGenesis() which is used for some special options, such as "-bench" (process command multiple times reporting timings), but then that function forwards to the actual 'command' function that was given as a argument to MagickCommandGenesis().
For "convert" that function is ConvertImageCommand() and is located in "wand/convert.c". This is the function that does the task of actually figuring out how to process the argument array given.
Here is an example of calling this function directly...
Code: Select all
/*
Bare minimal test of a direct call to ConvertImageCommand()
Actually this is basically what the "convert" command does.
Compile with...
gcc -I/usr/include/ImageMagick -lMagickWand -lMagickCore \
convert_equiv.c -o convert_equiv
*/
#include <stdio.h>
#include "magick/studio.h"
#include "magick/exception.h"
#include "magick/exception-private.h"
#include "magick/image.h"
#include "wand/MagickWand.h"
#include "wand/convert.h"
int main(int argc, char **argv)
{
MagickCoreGenesis(argv[0],MagickFalse);
{
int arg_count;
char *args[] = { "program_name", "-size", "100x100", "xc:red",
"(", "rose:", "-rotate", "-90", ")",
"+append", "show:", NULL };
for(arg_count = 0; args[arg_count] != (char *)NULL; arg_count++);
ImageInfo *image_info = AcquireImageInfo();
ExceptionInfo *exception = AcquireExceptionInfo();
MagickBooleanType status =
ConvertImageCommand(image_info, args_count, args, NULL, exception);
if (exception->severity != UndefinedException)
{
status=MagickTrue;
CatchException(exception);
}
if (status == MagickFalse)
fprintf(stderr, "Error in call\n");
image_info=DestroyImageInfo(image_info);
exception=DestroyExceptionInfo(exception);
}
MagickCoreTerminus();
}
The function itself is however not straight forward and complex code due to the need to handle IMv5 Legacy handling. The bulk of the function can also be ignored to an extent as it simply contains syntax checking. The actual read operation code (in IMv6) is in "wand/mogrify.c" and is called using the FireImageStack() macro. -- I did say it was complex!
IMv7 "magick" on the other hand is much more straight forward. No 'macro' code, that hides alot of the processing. Its functions (in "MagicWand/magick-cli.c") first handle 'special' requirements (eg "-version" "-list" "-script" otpions) then calls either a ProcessCommandOptions() or a ProcessScriptOptions() to handle options from a argument array (command line) or from a file stream (script). It calls the appropriate functions in "MagickWand/operation.c" to actually process the options in terms of a special MagickWand structure.
This install handling is 'mostly settled' but could still have some changes as development proceeds. IMv7 handling will replace the old IMv6 option handling. And "magick" command replaces "convert".