This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: standalone build for IA
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 22, 2008
01:05 AM
standalone build for IA
Do we have any standalone build that we can install on our build machines just to build the IA projects?
(10) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 22, 2008
02:03 AM
Outside the Advanced Designer graphical design tool, you mean? Yes, there is a command-line tool called build.exe (just look in your IA installation folder).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 22, 2008
02:11 AM
so is it sufficient to copy this build folder to a different machine and build IA projects there?
This is required for automated builds and I dont want to install complete IA on the build machine.
This is required for automated builds and I dont want to install complete IA on the build machine.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 22, 2008
03:23 AM
Please see my answer in this thread: http://community.acresso.com/showthread.php?t=184295
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 17, 2008
11:33 PM
this is the same problem i am facing..
i want to do automated builds.
I CANT EXCEPT TO HAVE SAME DIRECTORY STRUCTURE AS ON MINE (for custom codes and panels)
What is the solution to this?
i want to do automated builds.
I CANT EXCEPT TO HAVE SAME DIRECTORY STRUCTURE AS ON MINE (for custom codes and panels)
What is the solution to this?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 18, 2008
03:57 AM
qqqqqq wrote:
this is the same problem i am facing..
i want to do automated builds.
I CANT EXCEPT TO HAVE SAME DIRECTORY STRUCTURE AS ON MINE (for custom codes and panels)
What is the solution to this?
Please see my question to your reposted question in the other thread: http://community.acresso.com/showthread.php?t=184691
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 19, 2008
01:29 AM
Simply replace all nessesary paths inside the project file. (inside your Makefile or Ant or whatever you use to build)
Then automated building works well.
Also you can think about installing IA under a specific build-user. Then you can remote log-in and with X-redirection or remote desktop stuff you can use the project builder gui...
Then automated building works well.
Also you can think about installing IA under a specific build-user. Then you can remote log-in and with X-redirection or remote desktop stuff you can use the project builder gui...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 10, 2008
01:42 PM
Looks to me you can't just simply copy the IA folder to another machine. Using build.exe, my install will pop up the "This was built with an unlicensed copy" dialog box. Running it under ant does the same thing as well.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 16, 2008
02:09 PM
You can buy a "no-GUI" version of IA for your build machine, cost us about half. Of course you need the GUI version for your developer too.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 16, 2008
03:57 PM
That's very interesting, this is the first time I hear about that! Where did you get this information? TIA!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 16, 2008
04:01 PM
When we had to buy IA, we asked if there was a discount for the build machine, and there is, it's a special license. If I try to launch the GUI on the build machine it fails, because it's not licensed for GUI, just for command line. (We run it through ant.)