OK, so I checked the path just before and just after the launch of
vcvarsall.bat. It adds to the path in both ends so to speak, and with what
appears to be typos (double backslash, double semicolon). At the end I listed
the probable places but in view of simplicity I will keep jom in its own
di
>
> Hi P.O. !
> Can someone point me to the correct place (or places)?
>
It should be put into the directory that vcvarsall.bat adds to PATH. For a
64-bit build this would typically be ..\Hostx64\x64 and ..\HostX86\x86 for
a 32-bit build. To be sure, just check PATH after calling vcvarsall.
Last
Dear Windows gurus,
In order to speed up building on Windows it is suggested in the WIKI to use
jom.exe. This is what the WIKI states:
Microsoft's nmake doesn't support multi-core builds. To enable faster parallel
multi-core builds, download jom from
https://download.qt.io/official_releases/jo
It has nagged me for a long time that in order to build ooRexx on
Windows, one needs to also have an old Windows SDK installed. According
to a fairly recent exchange between Erich and Rick, this can be
accomplished by requesting XP(!) support when installing the free Visual
Studio Community edi
One more thingyou'll need to ensure that rxapi is killed before
starting the second build so that the proper one gets started up in the
later stages of the second build.
Rick
On Wed, Nov 28, 2012 at 1:33 PM, Mark Miesfeld wrote:
> On Wed, Nov 28, 2012 at 10:08 AM, David Ashley
> wrote:
>
On Wed, Nov 28, 2012 at 10:08 AM, David Ashley wrote:
> Can a 64-bit version of Windows build both the 32 and 64-bit version of
> ooRexx? If so, how do I set that up?
>
David,
I think it can, but I have not actually set it up to do it. You will just
need to cross-compile the 32-bit version.
Th
Yes, it is driven by which option of vcvarsall you specify. The default is
x86, which builds in 32-bit mode. If you specify x64, it builds in 64-bit
mode.
Rick
On Wed, Nov 28, 2012 at 1:08 PM, David Ashley wrote:
> Can a 64-bit version of Windows build both the 32 and 64-bit version of
> ooRe
Can a 64-bit version of Windows build both the 32 and 64-bit version of
ooRexx? If so, how do I set that up?
I am trying to set up a nightly build of ooRexx for Windows.
David Ashley
--
Keep yourself connected to Go Par
Mark,
On 09.02.2010 19:26, Mark Miesfeld wrote:
> Since the Windows SDKs are free, the build requirement does not seem
> to me to be a problem. But, it could mean someone has to update their
> SDK level. Some people might see that as a problem.
>
> So, I've been toying with the idea of adding a
On Tue, Feb 9, 2010 at 10:26 AM, Mark Miesfeld wrote:
> Rony's previous post reminded me that I meant to bring this up on the list.
>
> To build ooDialog now requires the Windows headers to be at least at
> the Vista level. ...
Following up on myself.
I should have added that the Windows build
Rony's previous post reminded me that I meant to bring this up on the list.
To build ooDialog now requires the Windows headers to be at least at
the Vista level. And, at some point in the future, probably as soon
as I get a chance to start working on Windows 7, ooDialog might
require the Windows
11 matches
Mail list logo
