Export pulsecore and pulsecommon header file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>
>On Tue, 07.04.09 15:25, Colin Guthrie (gmane at colin.guthr.ie) wrote:
>
>>
>> 'Twas brillig, and Lennart Poettering at 07/04/09 13:56 did gyre and
>gimble:
>>> On Tue, 07.04.09 16:19, Zhang, Xing Z (xing.z.zhang at intel.com) wrote:
>>>
>>>> Hi Lennart:
>>>> 	Could you have some comments on this patch
>>>
>>> See no patch! Did you forget to attach it?
>>
>> It was in the previous message on the thread:
>>
>> <http://permalink.gmane.org/gmane.comp.audio.pulseaudio.general/3098>
>
>Ah, ok. somehow i missed that.
>
>Zhang, what is the reason for doing your own install-pulse-headers
>targets? Why not just add them to some form of standard automake
>_HEADERS?

It is for making module developed by installed headers can be easily merged to upstream.
With standard automake HEADERS all headers will be located at one directory(eg. /usr/include/pulse_xxx/), programmers may arrange their files as below pattern:
#include <core.h>

This will kill when push to upstream. So I build same hierarchy as PA src to avoid painful rebasing works.

>
>Lennart
>
>--
>Lennart Poettering                        Red Hat, Inc.
>lennart [at] poettering [dot] net         ICQ# 11060553
>http://0pointer.net/lennart/           GnuPG 0x1A015CC4
>_______________________________________________
>pulseaudio-discuss mailing list
>pulseaudio-discuss at mail.0pointer.de
>https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss



[Index of Archives]     [Linux Audio Users]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux