Linker Error Unresolved External Referenced From
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Linker Error: Unresolved external (C++ Builder 6.0) up vote 0 down vote favorite I have a routine in C++ Builder 6 that send a file to webserver via HTTP Post, and when compile the project show these error messages from Linker: [Linker Error] Unresolved external"__fastcall Idmultipartformdata::TIdMultipartFormDataStream()" referenced from C:\Users\Admin\Documents\ProjCB6\Unit1.obj. Then; How I can do for resolved this problem? Thanks in advance! Here leave used source code => void HTTP() { TStringStream *response=new TStringStream(""); TIdMultiPartFormDataStream *stream=new TIdMultiPartFormDataStream(); TIdHTTP *IdHTTP1 = new TIdHTTP(NULL); try { IdHTTP1->Request->ContentType=stream->RequestContentType; stream->AddFormField("file1","doc"); stream->AddFile("file1","c:\\3.doc","doc"); stream->Position = 0; IdHTTP1->Post("http://172.16.8.186/doc/up.php",stream,response); Memo1->Lines->LoadFromStream(response); response->Free(); stream->Free(); IdHTTP1->Free(); } catch(...) { response->Free(); stream->Free(); IdHTTP1->Free(); } } c++builder indy c++builder-6 share|improve this question edited Mar 3 '14 at 10:12 manlio 10.7k103050 asked Mar 2 '14 at 1:47 Luiz Eduardo 39110 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote accepted C++Builder 6 shipped with Indy 8. TIdMultipartFormDataStream was introduced in Indy 9. The fact that your code compiles at all means that your project is using Indy 9 or Indy 10 header files, but the project might have a reference to the ol
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up How do I solve an unresolved external when using C++ Builder packages? up vote 6 down vote favorite 4 http://stackoverflow.com/questions/22122864/linker-error-unresolved-external-c-builder-6-0 I'm experimenting with reconfiguring my application to make heaving use of packages. Both I and another developer running a similar experiment are running into a bit of trouble when linking using several different packages. We're probably both doing something wrong, but goodness knows what :) The situation is this: The first package, PackageA.bpl, contains C++ class FooA. The class is declared with the PACKAGE directive. The second package, PackageB.bpl, contains a class inheriting http://stackoverflow.com/questions/2727001/how-do-i-solve-an-unresolved-external-when-using-c-builder-packages from FooA, called FooB. It includes FooB.h, and the package is built using runtime packages, and links to PackageA by adding a reference to PackageA.bpi. When building PackageB, it compiles fine but linking fails with a number of unresolved externals, the first few of which are: [ILINK32 Error] Error: Unresolved external '__tpdsc__ FooA' referenced from C:\blah\FooB.OBJ [ILINK32 Error] Error: Unresolved external 'FooA::' referenced from C:\blah\FooB.OBJ [ILINK32 Error] Error: Unresolved external '__fastcall FooA::~FooA()' referenced from blah\FooB.OBJ etc. Running TDump on PackageA.bpl shows: Exports from PackageA.bpl 14 exported name(s), 14 export addresse(s). Ordinal base is 1. Sorted by Name: RVA Ord. Hint Name -------- ---- ---- ---- 00002A0C 8 0000 __tpdsc__ FooA 00002AD8 10 0001 __linkproc__ FooA::Finalize 00002AC8 9 0002 __linkproc__ FooA::Initialize 00002E4C 12 0003 __linkproc__ PackageA::Finalize 00002E3C 11 0004 __linkproc__ PackageA::Initialize 00006510 14 0007 FooA:: 00002860 5 0008 FooA::FooA(FooA&) 000027E4 4 0009 FooA::FooA() 00002770 3 000A __fastcall FooA::~FooA() 000028DC 6 000B __fastcall FooA::Method1() const 000028F4 7 000C __fastcall FooA::Method2() const 00001375 2 000D Finalize 00001368 1 000E Initialize 0000610C 13 000F ___CPPdebugHook So the class definitely seems to be exported and available to link. I can see entries for the specific things ILink32 says it's looking for and not finding. Running TDump on the BPI file shows similar entries. Other info The class does descend from TO
Swedish Traditional Chinese Turkish | Location All Other RegionsASEANAustralia/New ZealandBeneluxD-A-CHGreater ChinaLatin AmericaNordicTaiwanUK and IrelandUS and CaribbeanCountriesBrazilCanadaFranceIndiaItalyJapanKorea (South)Russian FederationSpain Embarcadero Home Watch, Follow, & Connect with Us Share This Communities Articles Blogs Resources Downloads Help Submit Translation Printer-friendly http://edn.embarcadero.com/article/27343 EDN » C++Builder » Programming Show All [All] Unresolved external '_main' referenced from c0x32.obj By: Vincent Drake Abstract: Common error for beginning windows programmers. Question When I compile my windows application, I receive the http://www.richelbilderbeek.nl/CppLinkErrorUnresolvedExternal_Form2.htm error message "Unresolved external '_main' referenced from <path>c0x32.obj" Answer What this error really means is that the linker cannot find the entry-point function for your program. 'c0x32.obj', which is the startup code for a linker error console application, is asking the linker to find a function named 'main', the standard C/C++ entrypoint. The linker has searched the project's object files and libraries, but cannot find the 'main' function. This kind of error is usually caused by some mix-up between the intended project type and the actual project type. For instance, if you chose File, New, Console Wizard, checking 'Console Application', but proceeded to write a linker error unresolved windows-style application, with a WinMain entrypoint, this is exactly the error you would receive. To remedy the problem, you would create a new project, of the correct type, and add your source files to the new project. If compiling from the command line, the "target" options are analogous to the project type, and must likewise, be consistent with the application you're writing. The following list shows the BCC32.EXE options and their intended targets: -W Target is Windows application ("WinMain" entrypoint) -TC Target is console application ("main" entrypoint) -WD Target is a DLL ("DllMain" entrypoint) Latest Comments View AllAdd NewRSSATOM Move mouse over comment to see the full text Reply Posted by totte karlsson on Jul 09 2014Unresolved external '_main' referenced from c0x32.objSHould it not be -tW ??Reply Posted by Dániel Finta on Feb 20 2008re: Unresolved external '_main' referenced from c0x32.objOK! I solve this little puzzle. XD The problem was so simple I always overlooked it. I used this 'target:: dependents' and just 1 rule - the linker - so this messed up the thing. The correct...Reply Posted by Dániel Finta on Feb 18 2008Unresolved external '_main' referenced from c0x32.objMy problem can't be solved that simple! I'm compiled (and linked) a ton
Error] Unresolved external '_Form2' referenced from [...]\UNIT1.OBJ
Cause This error occurs when you have added a second TForm to your project (using 'File | Include Unit Hdr'), but without having done 'Project | Add to Project | Unit2.cpp' Solution Add the Unit to the Project: do 'Project | Add to Project | Unit2.cpp'. Go back to Richel Bilderbeek's C++ page. Go back to Richel Bilderbeek's homepage.