< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] Problem while installing resiprocate


I think the definition of USE_SSL is in the resiprocate/configure.ac (or configure.status) but I dont uderstand the syntax. Do you think the problem is in one of those files?

2016-05-09 14:49 GMT-03:00 Mateus Bellomo <mateusbellomo@xxxxxxxxx>:
I'm trying to find where USE_SSL is defined but I'm not finding it. I noticed that in some .vcxproj files there is some tags like this:

<PreprocessorDefinitions>WIN32;_DEBUG;_CONSOLE;BOOST_ALL_NO_LIB;_WIN32_WINNT=0x0501;USE_S
SL;LEAK_CHECK;%(PreprocessorDefinitions)</PreprocessorDefinitions>

Do you know where I could find this?

2016-05-09 11:49 GMT-03:00 Scott Godin <sgodin@xxxxxxxxxxxxxxx>:
I did recently add more USE_SSL defines to the reTURN code.  Perhaps the linux builds don't set the pre-processor define correctly.

Scott

On Mon, May 9, 2016 at 8:43 AM, Mateus Bellomo <mateusbellomo@xxxxxxxxx> wrote:
I don't know if there is a fancy way (I have never used gitk) to do this but I find the commit that change /resiprocate/reTurn repo and I commented all the

#ifdef USE_SSL
#endif

(just the ifdef not what was inside of it) added in that commit and it is compiling now. I think the flag USE_SSL is not being set as it supposed to be.

I will check again later (I'm going to a class now) if I could find the problem with the USE_SSL.

By the way, I don't know what information I should give you to identify that commit so I will put here what I see in the gitk window:

SHA1 id: e3958145c62d0d5237414e535ca451d91ebffa76
date: 2016-04-06 12:58:06
author: Scott Godin


2016-05-09 7:10 GMT-03:00 Daniel Pocock <daniel@xxxxxxxxxx>:


On 07/05/16 19:28, Mateus Bellomo wrote:
> I tried to compile again the reSIProcate and I'm getting the same error
> (I'm running on Debian jessie 8.3 and I just clone again the reSIProcate
> repository).
>
> Maybe some of the last commits caused it (the version I got like one
> month ago wasn't with this issue).
>

Could you try looking through the history of that source file or that
part of the tree with gitk and see if you can spot any changes there?
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel


_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel