Re: [fpc-pascal] 2.2.2 INSTALL PROBLEM
Hi John! I saw someone else that posted a similar issue. Are you using Vista? If so, this might help: * **Right-click** (not the usual left-click) the FPC folder from My Computer and select "Options" from the drop-down list (bottom entry). * There are 4 tabs at the top of the new window, one of them says "Security". Select that one and click the "Edit..." button (a window may pop up, asking for your permission to continue - Yes, continue...). * There's a list of groups/users and underneith that, a list of access rights. First make sure there's a group called "Users" in that first list (it should say something like "Users (John-PC\Users)"). If it isn't there, click the "Add..." button, in the next window click "Object Types.." and select (checkmark) "Users" then hit OK on this and the previous window. * If "Users" is already in the list, highlight it and from the list below select the "Full Control" in the "Allow" column - it will automatically select "Modify" as well, but will leave "Special Permissions" unselected. That;s ok, so leave it as that and click the "OK" button. A window will show what it's doing - applying these new security settings to the FPC folder and all subfolders / files. Now remember that in doing so, any user (Standard OR Administrator) on your computer can add/edit/delete folders and files in your FPC folder. If that's too much of a security risk for you, either upgrade your own user account to have Administrator rights (Start -> type "User" and select "User Accounts" from the program list -> Select "Change your account type") -OR- you can specifically select the FP.CFG file and apply these settings as outlined above to just that file instead of the whole FPC folder. Hope that did the trick for you, but use at your own risk ;-) -- Mike John Youngquist wrote: I JUST GOT 2.2.2 TO REPLACE MY 2.2.0 VERSION. When I compile a file that worked fine before it aborts immediately WITH A MESSAGE: "UNABLE TO OPEN: C:\FPC\2.2.2\BIN\i86-WIN32\fp.cfg Yet this file exists in this directory. Whats wrong? THANKS JY ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] How do I add a TComponent to TPanel dynamically?
Hi Danie, Other than what was pointed out with create/destroy, wouldn't it create a memory leak with the NEW? procedure TForm1.Button1Click(Sender: TObject); begin if pTopCV = nil then begin NEW( pTopCV ); pTopCV^ := TControlVolume.Create(PanelDraft); Instead, simply do: if not assigned(pTopCV) then begin pTopCV^ := TControlVolume.Create(Paneldraft); (Same goes for the pTopCV.next entry). -- Mike ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] License question about some sysutils .inc files
Hello everyone! I just happened to see the license on fina.inc / finah.inc and a few other includes by Gertjan Schouten, which are used in SysUtils (/rtl/objpas/sysutils). They're released under the GNU GPL, but don't mention anything about the special exception/persmission (COPYING.FPC). So, what would be the status of using SysUtils in a non-GPL (or compatible) licensed product in this case? Mike ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] SSocket: TSocketServer.StopAccepting
Hello Hansi, I am using Synapse for all my socket work, so this might be a bit different for you. But for a blocking listener in a thread (waiting at an Accept), I call AbortSocket. It immediately stops all work on the socket and lets you do the things you need to do. I'm sure there's a similar "Abort" function in the package you are using. -- Mike ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] FPC for FreeBSD AMD64?
I can see x86_64-freebsd in the FPC make file, so you ought to be able to build it with the source. Just add the parameters OS_TARGET=freebsd and CPU_TARGET=x86_64 -- Mike Francisco Reyes wrote: Are there any plans for a FreeBSD AMD64 version? Sometime ago I tried to work on this and since I am not very familiar with FPC yet I could not get very far. If there are currently no set plans for this port, anyone would be willing to do some heavy hand-holding for a new users to work on this? :-) I really would like to use FPC, since I like Pascal much more than C/C++, but I will need my programs to run in both FreeBSD i386 and AMD64. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] external .so linking in Linux w/2.5.1 rev 13680 (Sep 8 09)
Hi All! I've noticed that someone made a headstart with a unit to bind with FUSE in FreePascal at http://bugs.freepascal.org/view.php?id=12218. I've taken the last two entries (FUSE-2008-12-20-3.PP and Test-2008-12-20-3.PP) and modified the test file on line 88 to use the move() function instead of memcpy() -- and so eliminating the need for the "libc" unit. It compiles, but it fails at linking with this error: ... Linking Project1 /usr/bin/ld: cannot find -lfuse ... Okay, strange, nowhere do I see "fuse" specified. But upon closer inspection, it turns out something this gets lost in translation. For example, in the FUSE-2008-12-20-3.PP file, it contains: ... const FUSELIBFile = 'libfuse.so.2'; function fuse_main_real(aARGC : Integer; aARGV: PPChar; aOperations : TOperationsP; aOperationsSize : size_t; aUserData : Pointer) : Integer; cdecl; external FUSELIBFile; ... But in the link.res file I see: ... INPUT( -lfuse ) ... Even if I were to specify: ... const FUSELIBFile = '/lib/libfuse.so.2'; ... Then the link.res file tries to use: ... INPUT( -l/lib/libfuse ) ... So, where's the rest of the library's name? Is it a bug? Did I make a mistake on my end? ( And yes, that library is actually available on my system ) As noted in the subject, I'm using FPC 2.5.1 SVN rev 13680 from September 8th, x86_64 Linux (ppcrossx64). Kernel: 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 19:25:34 UTC 2009 x86_64 GNU/Linux -- MG ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] external .so linking in Linux w/2.5.1 rev 13680 (Sep 8 09)
Thanks Jonas. I could have sworn I had it installed and never bothered to check. Shows that one should never assume ;-) But it's good to you explained this linker behaviour though, for future reference. -- MG ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Question about ror / rordword...
Quick question: Is there any particular reason why the system function ror() (in /fpc/rtl/inc/systemh.inc) has been divided up into rorbyte, rordword and rorqword (and respectively for rol() ) instead of being overloaded? ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Question about ror / rordword...
Makes perfect sense, thanks for the quick answer :-) Florian Klaempfl wrote: Ror/rol are very sensitive against data type changes so this ensures you get always the desired result. While x shr 1 has the same result if the value fits in x, ror(x,1) has different results if x is a byte, word or dword even if it's value is e.g. 1. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
