These are chat archives for IndySockets/Indy

2nd
Mar 2017
Sam B
@SamBirnbaum
Mar 02 2017 00:54
@rlebeau Hi, sorry to bother you again, based on the instructions, I was looking for the batch command file FULLD_XE5 inside the zip file in the lib folder. Not there. There is FULLC_XE5.bat that looks for c++ only. Is that an oversight, is there another automated way to do this ?
Remy Lebeau
@rlebeau
Mar 02 2017 01:11
@SamBirnbaum Indy stopped using command-line scripts for Delphi in like 2010, they are only needed for C++Builder. For Delphi, you can just open and install the projects directly from the IDE.
Sam B
@SamBirnbaum
Mar 02 2017 01:35
@rlebeau Ok, is the dpk package #190 the correct one for xe5?
Remy Lebeau
@rlebeau
Mar 02 2017 01:36
@SamBirnbaum yes
Sam B
@SamBirnbaum
Mar 02 2017 01:40
@rlebeau Thank you. You and the rest of the Indy team are great. Thanks for taking the time doing this. If there is anything that I ever help you with, don't hesitate to email me.
Sam B
@SamBirnbaum
Mar 02 2017 12:04
@rlebeau Quick question, I have the version of XE that includes C++. Do I run the FULLC_XE5 batch control as well ? and if so do I run that first ? thanks again
Sam B
@SamBirnbaum
Mar 02 2017 16:31
@rlebeau Hi, Trying to follow the instructions that I downloaded and I am running into a problem. I removed Indy10 from the IDE, removed all the associated files from all the folders. I opened IndySystem190.dpk and I compiled it. It is not generating the bpl file so that the next step compiling IndyCore190.dpk can't find the IndySystem190. What am I doing wrong - Need help
Remy Lebeau
@rlebeau
Mar 02 2017 16:51
@SamBirnbaum Yes, it should be generating the BPLs. It likely just puts it where you are not expecting. Did you search the IDE's normal output paths? Like %MyDocuments%\RAD Studio\<version>\Bpl? Since you are dealing with C++, you might consider trying Malcolm Smith's precompiled binaries (http://www.mjfreelancing.com/indy.htm). It is not the absolute lately SVN version of Indy, but it is close.
Sam B
@SamBirnbaum
Mar 02 2017 17:06
@rlebeau Actually I am dealing Delphi, but I have the product that has C++ as well. I placed the download software in the folder c:\Indy10 so I will search the entire C drive and see if it placed it somewhere. BTW, there is a Group project for 190, what is that for ?
Sam B
@SamBirnbaum
Mar 02 2017 17:14
Found it. I guess I should have put the downloaded software in a folder under rad studio. Will have to redo it after I come back from the airport.
Thanks again. Sorry for bothering you.
Remy Lebeau
@rlebeau
Mar 02 2017 17:17
@SamBirnbaum Indy doesn't need to be put under RAD Studio's folder (I don't do that). As for the Project Group, that allows you to compile and install all 5 Indy packages at one time instead of individually.
Sam B
@SamBirnbaum
Mar 02 2017 21:32
@rlebeau Hi, still receiving the same error 502 bad gateway. I remove all the dcu's that I thought might be needed to be regenerated and I still get the same error. Is it possible the XE 5 is the problem ?
Remy Lebeau
@rlebeau
Mar 02 2017 21:38
@SamBirnbaum I don't see how, since this is an HTTP issue, not a Delphi issue
Sam B
@SamBirnbaum
Mar 02 2017 21:48
@rlebeau I agree with that statement but we know that your exe worked. What other dcu's should be removed ? and from where ?
I am assuming that all the required *.pas files are in the download file indy10_5396.zip
Remy Lebeau
@rlebeau
Mar 02 2017 22:38
@SamBirnbaum yes
@SamBirnbaum did you check to make sure your updated app is now sending a different HTTP request and not the old one?
Sam B
@SamBirnbaum
Mar 02 2017 23:06
@rlebeau That is weird. The accept-encoding still has identity in it.
Also I am getting an error about loading dclIPIndyIpll190.bpl - Not a valid win32 application
Remy Lebeau
@rlebeau
Mar 02 2017 23:08
@SamBirnbaum then you are not using the newer Indy version, your app is still compiling against the old version
Sam B
@SamBirnbaum
Mar 02 2017 23:10
@rlebeau I removed all the dcu's and replaced them with the ones that were downloaded.
@rlebeau All the old DCUs were moved to sub directories.
Remy Lebeau
@rlebeau
Mar 02 2017 23:13
@SamBirnbaum what about the old PAS and BPI/BPL files?
Sam B
@SamBirnbaum
Mar 02 2017 23:13
II can trap the traffic to the location where the header is being built. Will let you know.
The old pas files and the bpl files. Did not know about the BPI files. What are they ?
Remy Lebeau
@rlebeau
Mar 02 2017 23:18
@SamBirnbaum link libs for the BPLs
Sam B
@SamBirnbaum
Mar 02 2017 23:21
@rlebeau The pas files are all new (dated 3/1/2017) let check on the bpi files
@rlebeau Found thenew BPI files will make sure they are the ones that I am using. What about cdlIPIndyImpl190.bpl ?
Remy Lebeau
@rlebeau
Mar 02 2017 23:35
@SamBirnbaum dcl BPLs are design-time packages. IPIndyImpl is not an Indy package, it is an Embarcadero package that uses Indy internally for things like DataSnap and such.
Sam B
@SamBirnbaum
Mar 02 2017 23:40

@rlebeau Oh. These were the original bpls that I had:
IndyCore190.bpl
IndyIPClient190.bpl
IndyIPCommon190.bpl
IndyIPServer190.bpl
IndyProtocols190.bpl
IndySystem190.bpl

These were date 12/7/2013

However, after I compiled the 5 DPK files I only had
IndyCore190.bpl
IndyProtocols190.bpl
IndySystem190.bpl

These 3 replaced the 5 above as I removed the 5 above.

Remy Lebeau
@rlebeau
Mar 02 2017 23:43
@SamBirnbaum The only packages that belong to Indy are IndySystem, (dcl)IndyCore, and (dcl)IndyProtocols, the rest are Embarcadero's.
Sam B
@SamBirnbaum
Mar 02 2017 23:50
@rlebeau Ok. I will move them back into that directory. HAve to find again where the header is being prepared.
@rlebeau The .pas file are all new. idHTTP.pas was created on 12/15/2016 , IdHTTPHeaderInfo.pas was created 12/28/2015. does that sound right ?
@rlebeau Need to get a bite to eat. Can't think straight anymore.
Sam B
@SamBirnbaum
Mar 02 2017 23:56
@rlebeau Will be back shortly