Re: [Oorexx-devel] ooDialog - makeDLL - include paths for .h files
The rc compiler should search the INCLUDE path for .h files. On Windows the INCLUDE environment variable has the same format as PATH, but will not exist unless you have explicitly set it. I.e.: set INCLUDE=C:\ooRexx\samples\listview\rc;C:\ooRexx\samples\treeview\rc Ah-ha! I just knew it was a doh! question. Of course - the environment variables. How could I forget them? Many thanks again, Oliver -Original Message- From: Mark Miesfeld [mailto:miesf...@gmail.com] Sent: 04 April 2012 17:19 To: Open Object Rexx Developer Mailing List Subject: Re: [Oorexx-devel] ooDialog - makeDLL - include paths for .h files On Wed, Apr 4, 2012 at 10:52 AM, Oliver Sims oliver.s...@simsassociates.co.uk wrote: I'm using Mark's program 'makeDLL.rex' to make a DLL (so I can explain how to do it using RC.exe in the Guide). I'm having trouble with including the .h files. It seems that I have to copy them all into the makeDLL.rex folder. Well, I was going to say the 'easist way', but I guess I'll say 'one way' is to be sure the include statement for the .h file, in the rc file, correctly points to the .h file. The easiest way is to have the .rc file and the .h file in the same directory and just include the .h file name. The rc compiler should search the INCLUDE path for .h files. On Windows the INCLUDE environment variable has the same format as PATH, but will not exist unless you have explicitly set it. I.e.: set INCLUDE=C:\ooRexx\samples\listview\rc;C:\ooRexx\samples\treeview\rc Right now, at least some of the .rc files in the user guide exercises are set up in a way that is most convenient for building and packaging the Windows distribution. This does not make them a good example for showing someone unfamiliar with the compilation process how to use makeDLL.rex. I would use a simple example where all the files are in the same directory to show how to compile a resource file. Then note that the process is more complex if you start putting files in different directories. And that, in that case, the different files specified in the .rc file have to be specified in a way that the rc compiler can find them. Note that if you start getting messages like: CustomerView.rc(85) : error RC2135 : file not found: .\customer\bmp\Customer.ico you need to change the .\customer\bmp\Customer.ico to something else that points correctly to Customer.ico -- Mark Miesfeld -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] ooDialog - makeDLL - include paths for .h files
I'm using Mark's program 'makeDLL.rex' to make a DLL (so I can explain how to do it using RC.exe in the Guide). I'm having trouble with including the .h files. It seems that I have to copy them all into the makeDLL.rex folder. I tried adding the correct path to my PATH, but no luck. So: How do I get RC.exe to see the folder where my includes are? Many thanks, Oliver PS: I strongly suspect there's a doh! answer to this! -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooDialog - makeDLL - include paths for .h files
On Wed, Apr 4, 2012 at 10:52 AM, Oliver Sims oliver.s...@simsassociates.co.uk wrote: I'm using Mark's program 'makeDLL.rex' to make a DLL (so I can explain how to do it using RC.exe in the Guide). I'm having trouble with including the .h files. It seems that I have to copy them all into the makeDLL.rex folder. Well, I was going to say the 'easist way', but I guess I'll say 'one way' is to be sure the include statement for the .h file, in the rc file, correctly points to the .h file. The easiest way is to have the .rc file and the .h file in the same directory and just include the .h file name. The rc compiler should search the INCLUDE path for .h files. On Windows the INCLUDE environment variable has the same format as PATH, but will not exist unless you have explicitly set it. I.e.: set INCLUDE=C:\ooRexx\samples\listview\rc;C:\ooRexx\samples\treeview\rc Right now, at least some of the .rc files in the user guide exercises are set up in a way that is most convenient for building and packaging the Windows distribution. This does not make them a good example for showing someone unfamiliar with the compilation process how to use makeDLL.rex. I would use a simple example where all the files are in the same directory to show how to compile a resource file. Then note that the process is more complex if you start putting files in different directories. And that, in that case, the different files specified in the .rc file have to be specified in a way that the rc compiler can find them. Note that if you start getting messages like: CustomerView.rc(85) : error RC2135 : file not found: .\customer\bmp\Customer.ico you need to change the .\customer\bmp\Customer.ico to something else that points correctly to Customer.ico -- Mark Miesfeld -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooDialog - makeDLL - include paths for .h files
Apparently, the Samples directory that I have does not contain the listview or treeview sub-directory. Should I have these directories? I also cannot find makedll.rex. I was also wondering if an ooRexx program can be compiled into an executable form, such that it would run as an exe file, or perhaps in a JVM environment. -Original Message- From: Mark Miesfeld [mailto:miesf...@gmail.com] Sent: Wednesday, April 04, 2012 1:19 PM To: Open Object Rexx Developer Mailing List Subject: Re: [Oorexx-devel] ooDialog - makeDLL - include paths for .h files On Wed, Apr 4, 2012 at 10:52 AM, Oliver Sims oliver.s...@simsassociates.co.uk wrote: I'm using Mark's program 'makeDLL.rex' to make a DLL (so I can explain how to do it using RC.exe in the Guide). I'm having trouble with including the .h files. It seems that I have to copy them all into the makeDLL.rex folder. Well, I was going to say the 'easist way', but I guess I'll say 'one way' is to be sure the include statement for the .h file, in the rc file, correctly points to the .h file. The easiest way is to have the .rc file and the .h file in the same directory and just include the .h file name. The rc compiler should search the INCLUDE path for .h files. On Windows the INCLUDE environment variable has the same format as PATH, but will not exist unless you have explicitly set it. I.e.: set INCLUDE=C:\ooRexx\samples\listview\rc;C:\ooRexx\samples\treeview\rc Right now, at least some of the .rc files in the user guide exercises are set up in a way that is most convenient for building and packaging the Windows distribution. This does not make them a good example for showing someone unfamiliar with the compilation process how to use makeDLL.rex. I would use a simple example where all the files are in the same directory to show how to compile a resource file. Then note that the process is more complex if you start putting files in different directories. And that, in that case, the different files specified in the .rc file have to be specified in a way that the rc compiler can find them. Note that if you start getting messages like: CustomerView.rc(85) : error RC2135 : file not found: .\customer\bmp\Customer.ico you need to change the .\customer\bmp\Customer.ico to something else that points correctly to Customer.ico -- Mark Miesfeld -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] ooDialog - makeDLL - include paths for .h files
On Wed, Apr 4, 2012 at 11:10 AM, Sanford Geiger sanford.gei...@live.com wrote: Apparently, the Samples directory that I have does not contain the listview or treeview sub-directory. Should I have these directories? No, I just made them up as an illustration. They don't exist. I also cannot find makedll.rex. makedll.rex is not a part of the ooRexx distribution. It is just a helper utility to compile a resource only DLL: /* makeDLL.rex */ -- Compile a resource script file to a resource only DLL (a binary resource.) -- Assumes, the Microsoft tools are in the path. -- First arg is the resource script file name, without the extension. The -- second arg is optional and can be used to rename the output DLL file. use arg cmdLine if arg(1, 'O') then return doHelp() parse var cmdLine inFile outFile . if outFile == then outFile = inFile inFile = inFile'.rc' if \ haveTools() then return doHelp() 'rc -r -fo'outFile'.res' inFile 'link' outFile'.res /NOENTRY /DLL /MACHINE:X86 /OUT:'outFile'.dll' return 0 -- Simplistic check for rc.exe to see if the tools are accessible. ::routine haveTools 'rc /? nul 21' rcRet = RC if rcRet 0 then do say rcexe or link.exe (or both) do not appear to be in the path. return .false end return .true ::routine doHelp say say makeDLL: compile a resource only DLL using Microsoft's tools. say 'rc.exe and link.exe must be in the path.' say say 'Syntax: makeDll rcFile [outFile]' say 'where rcFile is the input file, leave off the .rc extension.' say 'outFile is optional, used to rename the output file.' say say 'Examples:' say 'makeDll OpenWatcom' say ' Compiles OpenWatcom.rc producing OpenWatcom.dll.' say say 'makeDll OpenWatcom OpenWatcomMS' say ' Compiles OpenWatcom.rc producing OpenWatcomMS.dll.' return 0 was also wondering if an ooRexx program can be compiled into an executable form, such that it would run as an exe file, or perhaps in a JVM environment. No, there is no (easy, good) way to do that. What Oliver was talking about is compiling resources into a DLL for user by ooDialog. -- Mark Miesfeld -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
