Include file question [solved]

skottish · 2008-04-11 04:29:51

EDIT--

Good, no one answered yet. I should have mentioned that this is only an example. I'd like to know generically if this is possible with a general configure option and not just for this situation.

---

GEGL is now building against parts of FFmpeg. The include call looks like this for avformat.h:

#include <ffmpeg/avformat.h>

avformat.h on my system is in /usr/include/libavformat

Since there is no directory ffmpeg in the PATH anywhere, is there any parameter to pass to ./configure to get GCC to see avformat.h, or is it tied to ffmpeg/avformat.h? I have a working hack, but it's ugly!

Last edited by skottish (2008-04-13 05:15:53)

kakTuZ · 2008-04-12 19:19:20

Try running "configure --help". This gives some general hints.
You can pass additional include paths using environment variables. e.g. the dosbox configure file gives:

Some influential environment variables:
  CC          C compiler command
  CFLAGS      C compiler flags
  LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a
              nonstandard directory <lib dir>
  CPPFLAGS    C/C++/Objective C preprocessor flags, e.g. -I<include dir> if
              you have headers in a nonstandard directory <include dir>
  CPP         C preprocessor
  CXX         C++ compiler command
  CXXFLAGS    C++ compiler flags

skottish · 2008-04-12 21:28:46

kakTuZ wrote:

Try running "configure --help". This gives some general hints.
You can pass additional include paths using environment variables. e.g. the dosbox configure file gives:

Some influential environment variables:
  CC          C compiler command
  CFLAGS      C compiler flags
  LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a
              nonstandard directory <lib dir>
  CPPFLAGS    C/C++/Objective C preprocessor flags, e.g. -I<include dir> if
              you have headers in a nonstandard directory <include dir>
  CPP         C preprocessor
  CXX         C++ compiler command
  CXXFLAGS    C++ compiler flags

Thanks. I wrote this after trying standard flags to no avail. In particular I've used CPPFLAGS in other places to cope with FFmpeg's ever changing file structure. It's fine for swfdec, but failed miserably on gegl. The main difference though is that swfdec is looking for HEADER in the PATH. gegl is looking for DIRECTORY/HEADER. To isolate my question down a bit, if the compiler finds HEADER in the PATH somewhere, but not DIRECTORY/HEADER, will it use it?

Allan · 2008-04-13 01:00:51

No, it won't use it. You will pretty much have to edit the include line or create a symlink.

skottish · 2008-04-13 01:23:58

Allan wrote:

No, it won't use it. You will pretty much have to edit the include line or create a symlink.

Thanks Allan, that's along the lines of what I was thinking.

--edit--

I killed my other question just to try...

Last edited by skottish (2008-04-13 01:27:27)

skottish · 2008-04-13 01:45:53

Bump to ask yet another question. Does this constitute one of the ugliest, most inefficient hacks in history?

build() {
  cd $startdir/src/$pkgname-$pkgver
  find . -type f | xargs perl -pi~ -e 's/<ffmpeg\/avformat.h>/<libavformat\/avformat.h>/g;'
  ./configure --prefix=/usr 

...

Last edited by skottish (2008-04-13 01:48:47)

Allan · 2008-04-13 02:33:49

skottish wrote:

Bump to ask yet another question. Does this constitute one of the ugliest, most inefficient hacks in history?

Not quite... I have used a combination of "grep -l" and "sed" before. Now I just create a patch.

Arch Linux

#1 2008-04-11 04:29:51

Include file question [solved]

#2 2008-04-12 19:19:20

Re: Include file question [solved]

#3 2008-04-12 21:28:46

Re: Include file question [solved]

#4 2008-04-13 01:00:51

Re: Include file question [solved]

#5 2008-04-13 01:23:58

Re: Include file question [solved]

#6 2008-04-13 01:45:53

Re: Include file question [solved]

#7 2008-04-13 02:33:49

Re: Include file question [solved]

Board footer