[reSIProcate] Linking error

[Byron Campen]

	Sounds like we just need a dummy target. Something like
MethodHash.cxx: check_gperf MethodHash.gperf

.
.
.

check_gperf:
	<call gperf in some trivial way>

Now, as for nobody needing gperf, does that mean we should include  
all the generated code in the release?

Best regards,
Byron Campen

> On 8/24/06, Byron Campen <docfaraday at mac.com> wrote:
>>         Now, this brings up a point; does it make sense have the  
>> build check
>> for the presence of gperf before trying to generate MethodHash.cxx?
>> This build problem has wasted lots of time for many people.
>
> Absolutely! If somebody can figure out how to do this, it would be
> outstanding. In fact, nobody should need gperf unless they change the
> gperf files.
>
> Jason
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20060824/bc03cb5a/attachment.htm>