VC++: Intel and Alpha targets. How?
Marc -- msd@cadcentre.co.uk
Thursday, December 21, 1995
We've been developing VC++ 2.0 MFC applications on an Alpha NT
and now wish to build these projects on an Intel box.
When I tried to simply use my Alpha Makefile to build on the Intel, VC
told me that the Makefile did not contain any targets whose platforms
are supported by this installation of VC. And that I would need to
create a new target in order to build the project.
OK. So I then tried to create a new target :) by copying the settings ;)
from one of the targets previously created on the Alpha, but it wouldn't
allow me to make a copy :(
Why is it stopping me from copying the target? Do I have to typo in
again all my Alpha targets for the Intel? Has anyone any thoughts on
how this sort of cross-platform development is best tackled?
Thanks,
Marc.
Mike Blaszczak -- mikeblas@msn.com
Saturday, December 23, 1995
I've not started on the Alpha and gone to an Intel box, but I do know that if
you take an Intel project and move it to the Alpha, VC++ will automatically
add the targets to the project for you. If you have both boxes at your
disposal now, why not try it the other way around with a scratch project to
see what happens?
.B ekiM
----------
From: owner-mfc-l@netcom.com on behalf of Marc
Sent: Thursday, December 21, 1995 03:46
To: mfc-l@netcom.com
Subject: VC++: Intel and Alpha targets. How?
We've been developing VC++ 2.0 MFC applications on an Alpha NT
and now wish to build these projects on an Intel box.
When I tried to simply use my Alpha Makefile to build on the Intel, VC
told me that the Makefile did not contain any targets whose platforms
are supported by this installation of VC. And that I would need to
create a new target in order to build the project.
OK. So I then tried to create a new target :) by copying the settings ;)
from one of the targets previously created on the Alpha, but it wouldn't
allow me to make a copy :(
Why is it stopping me from copying the target? Do I have to typo in
again all my Alpha targets for the Intel? Has anyone any thoughts on
how this sort of cross-platform development is best tackled?
Thanks,
Marc.
Mark Simonton -- marksi@eskimo.com
Sunday, December 24, 1995
What you need to do is open the build.configurations and choose the
add button this will give you the option to "clone" either the retail
or debug configuration from a "non-supported" platform. Unfortunatly
this will not copy any non-default settings (.lib files, extra
defines, etc. ) from the cloned project it only gets all the files
from the original and sets the project with the target CPU's default
settings.
once again, the steps are:
open your project on the target platform
choose build menu
choose the configurations menu item
choose the add button from the configurations dialog
choose the configuration you wish to clone
choose OK
now set the default project to the newly added project.
try to build and fill in any missing settings needed to make
the project work.
Note: all newly added configurations will have the same target
directory of the form:
"project_name_filled_in_with_undedrscores_to_make_it_8_chars_long_terminated_by_a_digit"
Hope this helps.
Mark Simonton
On Sat, 23 Dec 95 01:54:12 UT, you wrote:
>I've not started on the Alpha and gone to an Intel box, but I do know that if
>you take an Intel project and move it to the Alpha, VC++ will automatically
>add the targets to the project for you. If you have both boxes at your
>disposal now, why not try it the other way around with a scratch project to
>see what happens?
>
>.B ekiM
>
>----------
>From: owner-mfc-l@netcom.com on behalf of Marc
>Sent: Thursday, December 21, 1995 03:46
>To: mfc-l@netcom.com
>Subject: VC++: Intel and Alpha targets. How?
>
>
>We've been developing VC++ 2.0 MFC applications on an Alpha NT
>and now wish to build these projects on an Intel box.
>
>When I tried to simply use my Alpha Makefile to build on the Intel, VC
>told me that the Makefile did not contain any targets whose platforms
>are supported by this installation of VC. And that I would need to
>create a new target in order to build the project.
>
>OK. So I then tried to create a new target :) by copying the settings ;)
>from one of the targets previously created on the Alpha, but it wouldn't
>allow me to make a copy :(
>
>Why is it stopping me from copying the target? Do I have to typo in
>again all my Alpha targets for the Intel? Has anyone any thoughts on
>how this sort of cross-platform development is best tackled?
>
>Thanks,
>Marc.
>
>
>
>
>
Marc -- msd@cadcentre.co.uk
Thursday, January 04, 1996
On Dec 21, 11:46am, Marc wrote:
> Subject: VC++: Intel and Alpha targets. How?
>
> We've been developing VC++ 2.0 MFC applications on an Alpha NT
> and now wish to build these projects on an Intel box.
>
> When I tried to simply use my Alpha Makefile to build on the Intel, VC
> told me that the Makefile did not contain any targets whose platforms
> are supported by this installation of VC. And that I would need to
> create a new target in order to build the project.
>
> OK. So I then tried to create a new target :) by copying the settings ;)
> from one of the targets previously created on the Alpha, but it wouldn't
> allow me to make a copy :(
>
> Why is it stopping me from copying the target? Do I have to typo in
> again all my Alpha targets for the Intel? Has anyone any thoughts on
> how this sort of cross-platform development is best tackled?
>
> Thanks,
> Marc.
>
>-- End of excerpt from Marc
On Dec 23, 1:54am, Mike Blaszczak wrote:
>
> I've not started on the Alpha and gone to an Intel box, but I do know that if
> you take an Intel project and move it to the Alpha, VC++ will automatically
> add the targets to the project for you. If you have both boxes at your
> disposal now, why not try it the other way around with a scratch project to
> see what happens?
>
> .B ekiM
>
>-- End of excerpt from Mike Blaszczak
Mike,
I did try out what you suggested but, unfortunately, it didn't change
things.
When I'm on the new platform (Alpha or Intel) I can't copy targets
created on the original platform. In fact VC won't even allow me to
view them.
Of course what we want is to be able to create Intel targets based on
our old Alpha ones, and then be able to update all targets (Alpha or
Intel) in sync, independent of what machine we're using at the time.
I definately tried this for a "Win32 Console Application" and
I think also for an MFC AppWizard (EXE).
Marc.
On Dec 24, 6:12pm, Mark Simonton wrote:
>
> What you need to do is open the build.configurations and choose the
> add button this will give you the option to "clone" either the retail
> or debug configuration from a "non-supported" platform. Unfortunately
> this will not copy any non-default settings (.lib files, extra
> defines, etc. ) from the cloned project it only gets all the files
> from the original and sets the project with the target CPU's default
> settings.
>
> Mark Simonton
>
>-- End of excerpt from Mark Simonton
Mark,
I'm using VC 2.0 and it doesn't have a 'build' menu containing a
'configurations' menu item. If that's a VC 4.x thing then I'm still
looking for a VC 2.0 solution as it would be a problem for us to
upgrade right now
Does anyone have any other thoughts on how to maintain a VC project
on Alpha NT and Intel NT?
Many thanks for anymore suggestions.
Marc.
Mark Simonton -- marksi@eskimo.com
Monday, January 08, 1996
Oh, I thought the compliler versions the same on all platforms. My
suggestion then is that you will need to keep seperate sets of
makefiles (or use makefiles and NMAKE and abandon the IDE) for each
platform, just copy the files over to the second machine and create a
project and then import the files into the project.
If you need the makefile to be portable across platforms and compiler
versions then you will need to use nmake instead of the IDE. if you
have access to sed here is a small sed script that can make a vc 4.0
makefile work across hardware platforms
<>
#wrapper.mak
CPU=$(PROCESSOR_ARCHITECTURE)
# substitute the current cpu setting in the link line
# for the original setting
# run namke on the created makefile
all:
sed "s/old_proc_architecture/$(CPU)/g" project.mak > proj$(CPU).mak
$(MAKE) proj$(CPU).mak "$(CFG)"
#end wrapper.mak
<>
note this assumes common compiler switches (or at least compilers that
will ignore invalid switches on the command line) and also that you
aren't compileing /wx (warnings == errors). The best is still a well
written human designed makefile.
Hope this is more help
Mark
----
On Thu, 4 Jan 1996 17:19:42 +0000, you wrote:
>
>On Dec 21, 11:46am, Marc wrote:
>> Subject: VC++: Intel and Alpha targets. How?
>>
>
[snip]
>
>Mark,
>
>I'm using VC 2.0 and it doesn't have a 'build' menu containing a
>'configurations' menu item. If that's a VC 4.x thing then I'm still
>looking for a VC 2.0 solution as it would be a problem for us to
>upgrade right now
>
>Does anyone have any other thoughts on how to maintain a VC project
>on Alpha NT and Intel NT?
>
>Many thanks for anymore suggestions.
>
>Marc.
>
>
>
| Вернуться в корень Архива
|