Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Neither of the errors you mentioned are compiler errors. Its unlikely they are caused by the compiler itself. They are probably coming from somewhere else in the call chain leading up to the compile.</p> <p>A short term solution would be to compile from the command line. MSBuild is the build engine Delphi uses under the hood. </p> <ol> <li>Edit whatever Indy files in the IDE as you normally would, save your changes then close the IDE.</li> <li>Open the <em>Rad Studio Command Prompt</em> from the start menu. This will make sure the proper environment variables are set to run the command line build. You could also use the standard command prompt and run rsvars.bat to accomplish the same thing.</li> <li>Use <code>cd</code> to change directories to the location of IndyProtocols.dpk</li> <li>Type <code>msbuild IndyProtocols.dpk /target:Build /p:config=Release</code></li> </ol> <p>If you want to do a debug version just change <code>/p:config=Release</code> to <code>/p:config=Debug</code>. Note that case is important when working with msbuild because the project files are xml, which is case sensitive.</p> <p>Also, for what its worth you should try to avoid making changes directly to the libraries shipped with the IDE. If you found a bug in a supplied library that you need fixed for a specific project you can usually get by with copying the offending file into your project's folder and making your changes to it there. You'll also likely need to copy several other dependent files as well. If you take this approach the compiler will inform you which dependents need to be copied with errors such as <code>Unit * was compiled with a different version of *.*</code></p> <hr> <p>Now if you really want to debug the IDE you can try but the <code>rtl</code> and <code>coreide</code> packages used throughout the IDE and are both compiled as release versions (no debugging info) so it may be difficult to determine what's causing the errors you're seeing.</p> <p>Anyways, you can run a second instance of the IDE with the IndyProtocols.dpk loaded in the project manager. Then use <code>Run &gt; Attach to Process</code> from the first IDE instance to attach the debugger to the second IDE instance. After that just try building IndyProtocols.dpk from the second IDE instance. If all goes as expected the debugger will catch the errors and let you break at where they occurred so you can dig around.</p>
    singulars
    1. This table or related slice is empty.
    1. POFailed to recompile the source code of indy10 on XE2
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USKenneth Cochran
    1. USKenneth Cochran
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYeah you are right. They are not compiler errors. And I will also not to change the libs of IDE directly. Thx!
      singulars
      1. PO
      1. USWilly
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload