Re: [Unicon-group] Svn Update

[Jafar Al-Gharaibeh]

Good to hear that it all worked at the end.

BTW, I also recently added the ability to do a parallel build. After the
configuration step and instead of just invoking "make" do:

 make -jN

Where N is the number of parallel tasks that make can run concurrently. I
typically run with N=2*Cores.

Cheers,
Jafar


On Tue, Jun 20, 2017 at 3:04 PM, Steve Wampler  wrote:

> On 06/20/2017 12:41 PM, Jeffery, Clint (jeffe...@uidaho.edu) wrote:
> > The event.u reference probably comes from an old uni/lib/deps.out or
> some such.  See commit r5068 or feel free to ask
> > questions.
>
> Thanks.  I ended up doing a:
>
> find . -type f | xargs grep -l -e "event\.u"
>
> and uncovered a file "makefile" in uni/lib dated from back in Feb.
> This was being used in place of the (newer) Makefile.
>
> Removing 'makefile' fixed the problem, but the same thing
> happened in uni/unidoc.  Removing the 'makefile' there
> allowed compilation to complete.
>
> However, there are a lot of 'makefile's laying arounc
> after the make Pure besides those two.  In particular:
>
>->find . -name makefile
>./uni/util/makefile
>./uni/ivib/makefile
>./uni/unidoc/docs/makefile
>./uni/unidep/makefile
>./uni/gui/ivib/makefile
>./uni/gui/guidemos/makefile
>./uni/gui/makefile
>./uni/xml/makefile
>./uni/unicon/makefile
>./uni/native/makefile
>./uni/parser/makefile
>./doc/unicon/makefile
>->
>
> Most of these (but not all) mask a new Makefile in the
> same directory:
>
>>for f in $(find . -name makefile); do
> >nf=$(dirname $f)
> >if [ -f $nf/Makefile ]; then
> >  echo $nf
> >fi
> >done
>./uni/util
>./uni/ivib
>./uni/unidep
>./uni/gui/ivib
>./uni/gui/guidemos
>./uni/gui
>./uni/xml
>./uni/unicon
>./uni/native
>./uni/parser
>->
>
> (the directories doc/unicon and uni/unidoc have "makefile", but no
> "Makefile")
>
> I suspect that while the build works the new Makefiles being masked aren't
> being used.  So I removed those 'makefile's (leaving the two that aren't
> masking a Makefile) and reran:
>
>   ./configure && make
>
> There were no more problems encountered.
>
> Thanks for the hint - that helped!
>
> -Steve
>
> --
> Steve Wampler -- swamp...@noao.edu
> The gods that smiled on your birth are now laughing out loud.
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Unicon-group mailing list
> Unicon-group@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/unicon-group
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group

Re: [Unicon-group] Svn Update

[Steve Wampler]

On 06/20/2017 12:41 PM, Jeffery, Clint (jeffe...@uidaho.edu) wrote:
> The event.u reference probably comes from an old uni/lib/deps.out or some 
such.  See commit r5068 or feel free to ask
> questions.

Thanks.  I ended up doing a:

find . -type f | xargs grep -l -e "event\.u"

and uncovered a file "makefile" in uni/lib dated from back in Feb.
This was being used in place of the (newer) Makefile.

Removing 'makefile' fixed the problem, but the same thing
happened in uni/unidoc.  Removing the 'makefile' there
allowed compilation to complete.

However, there are a lot of 'makefile's laying arounc
after the make Pure besides those two.  In particular:

   ->find . -name makefile
   ./uni/util/makefile
   ./uni/ivib/makefile
   ./uni/unidoc/docs/makefile
   ./uni/unidep/makefile
   ./uni/gui/ivib/makefile
   ./uni/gui/guidemos/makefile
   ./uni/gui/makefile
   ./uni/xml/makefile
   ./uni/unicon/makefile
   ./uni/native/makefile
   ./uni/parser/makefile
   ./doc/unicon/makefile
   ->

Most of these (but not all) mask a new Makefile in the
same directory:

   >for f in $(find . -name makefile); do
>nf=$(dirname $f)
>if [ -f $nf/Makefile ]; then
>  echo $nf
>fi
>done
   ./uni/util
   ./uni/ivib
   ./uni/unidep
   ./uni/gui/ivib
   ./uni/gui/guidemos
   ./uni/gui
   ./uni/xml
   ./uni/unicon
   ./uni/native
   ./uni/parser
   ->

(the directories doc/unicon and uni/unidoc have "makefile", but no "Makefile")

I suspect that while the build works the new Makefiles being masked aren't
being used.  So I removed those 'makefile's (leaving the two that aren't
masking a Makefile) and reran:

  ./configure && make

There were no more problems encountered.

Thanks for the hint - that helped!

-Steve
--
Steve Wampler -- swamp...@noao.edu
The gods that smiled on your birth are now laughing out loud.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group

Re: [Unicon-group] Svn Update

[Jafar Al-Gharaibeh]

Steve,

I  highly recommend doing a fresh checkout to avoid many of these issues.
svn couldn't keep things straight with this whole revision/unrevisioned
mix. As you mentioned, you have to manually remove/revert files for it to
work.

--Jafar

On Tue, Jun 20, 2017 at 2:41 PM, Jeffery, Clint (jeffe...@uidaho.edu) <
jeffe...@uidaho.edu> wrote:

> Steve,
>
>
> I renamed a class named Event in uni/lib awhile back. Its new name is
> Notification. Although it was in a package, people had complained that it
> was a conflict with a built-in function Event, and someone doing an import
> of the package could be surprised when their program no longer ran.
>
>
> The event.u reference probably comes from an old uni/lib/deps.out or some
> such.  See commit r5068 or feel free to ask questions.
>
>
> Clint
>
> --
> *From:* Steve Wampler 
> *Sent:* Tuesday, June 20, 2017 12:22:52 PM
> *To:* unicon-group@lists.sourceforge.net
> *Subject:* Re: [Unicon-group] Svn Update
>
> On 06/15/2017 11:38 PM, Jafar Al-Gharaibeh wrote:
>  > Status Update:
>  >
>  >While not done yet but the progress that has been made so far is
> enough to allow people to give the new changes a
>  > try. Basically, what we are trying to do is move a way from any
> "manual" configuration where end users don't have to
>  > edit files to define this or enable that to control whether a
> particular feature is enabled or not.  We are also leaving
>  > no chance of guessing on the end user part to get the correct
> configuration for an underlying platform. The
>  > configuration script should be able to figure it out on its own in the
> vast majority of cases. We will update the
>  > documentation on the website in the next few days on how to build or
> configure Unicon moving forward. The instructions
>  > are easy, checkout the sources and just do:
>  >
>  > ./configure && make
>  >
>  > And  that is all you need (crossing fingers).
>
> On my Linux/CentOS 7 system, I had a few problems:
>
> 'make Pure' - no issues.
>
> svn update - kept failing because it would find unversioned Makefiles
> and an occassional unversioned directory.  Kept removing those and
> rerunning the update until no more failures.
>
> ./configure && make - failed the first time on the make.  It
> printed out the old help message:
> ---
> UNIX: Run "make Configure name=system" or "make X-Configure
> name=system" or "make build name=system"
>where system is one of those in config/unix.
> Windows (MSVC): Run "nmake NT-Configure" or "nmake W-Configure".
> Windows (GCC): Run "make NT-Configure-GCC" or "make W-Configure-GCC".
> Windows (both): Then add the Unicon bin directory to your path.
> All: after configuration, run "make (or nmake) Unicon".
> ---
> A quick showed that the main Makefile hadn't been updated.
> Removed it, did an svn update on it and reran command.
>
> ./configure && make - (#2) no problems building icont, iconc, and unicon,
> and most of the *.icn code through compiling webup.icn.  Then:
> ---
> make[3]: *** No rule to make target `event.u', needed by `all'.  Stop.
> make[3]: Leaving directory `/disk/opt/svn/unicon/unicon/uni/lib'
> make[2]: *** [lib] Error 2
> make[2]: Leaving directory `/disk/opt/svn/unicon/unicon/uni'
> make[1]: *** [Unicon] Error 2
> make[1]: Leaving directory `/disk/opt/svn/unicon/unicon'
> make: *** [default] Error 2
> -
> There is a file 'event.u' in ipl/lib, but I can't figure out
> why Makefile in uni/lib thinks event.u needs to be built as
> it's not listed in UFILES!
>
> help?
>
> Thanks!
> Steve
>
> --
> Steve Wampler -- swamp...@noao.edu
> The gods that smiled on your birth are now laughing out loud.
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Unicon-group mailing list
> Unicon-group@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/unicon-group
>
> 
> --
> Check out the vibran

Re: [Unicon-group] Svn Update

[Jeffery, Clint (jeffe...@uidaho.edu)]

Steve,


I renamed a class named Event in uni/lib awhile back. Its new name is 
Notification. Although it was in a package, people had complained that it was a 
conflict with a built-in function Event, and someone doing an import of the 
package could be surprised when their program no longer ran.


The event.u reference probably comes from an old uni/lib/deps.out or some such. 
 See commit r5068 or feel free to ask questions.


Clint


From: Steve Wampler 
Sent: Tuesday, June 20, 2017 12:22:52 PM
To: unicon-group@lists.sourceforge.net
Subject: Re: [Unicon-group] Svn Update

On 06/15/2017 11:38 PM, Jafar Al-Gharaibeh wrote:
 > Status Update:
 >
 >While not done yet but the progress that has been made so far is enough 
 > to allow people to give the new changes a
 > try. Basically, what we are trying to do is move a way from any "manual" 
 > configuration where end users don't have to
 > edit files to define this or enable that to control whether a particular 
 > feature is enabled or not.  We are also leaving
 > no chance of guessing on the end user part to get the correct configuration 
 > for an underlying platform. The
 > configuration script should be able to figure it out on its own in the vast 
 > majority of cases. We will update the
 > documentation on the website in the next few days on how to build or 
 > configure Unicon moving forward. The instructions
 > are easy, checkout the sources and just do:
 >
 > ./configure && make
 >
 > And  that is all you need (crossing fingers).

On my Linux/CentOS 7 system, I had a few problems:

'make Pure' - no issues.

svn update - kept failing because it would find unversioned Makefiles
and an occassional unversioned directory.  Kept removing those and
rerunning the update until no more failures.

./configure && make - failed the first time on the make.  It
printed out the old help message:
---
UNIX: Run "make Configure name=system" or "make X-Configure name=system" or 
"make build name=system"
   where system is one of those in config/unix.
Windows (MSVC): Run "nmake NT-Configure" or "nmake W-Configure".
Windows (GCC): Run "make NT-Configure-GCC" or "make W-Configure-GCC".
Windows (both): Then add the Unicon bin directory to your path.
All: after configuration, run "make (or nmake) Unicon".
---
A quick showed that the main Makefile hadn't been updated.
Removed it, did an svn update on it and reran command.

./configure && make - (#2) no problems building icont, iconc, and unicon,
and most of the *.icn code through compiling webup.icn.  Then:
---
make[3]: *** No rule to make target `event.u', needed by `all'.  Stop.
make[3]: Leaving directory `/disk/opt/svn/unicon/unicon/uni/lib'
make[2]: *** [lib] Error 2
make[2]: Leaving directory `/disk/opt/svn/unicon/unicon/uni'
make[1]: *** [Unicon] Error 2
make[1]: Leaving directory `/disk/opt/svn/unicon/unicon'
make: *** [default] Error 2
-
There is a file 'event.u' in ipl/lib, but I can't figure out
why Makefile in uni/lib thinks event.u needs to be built as
it's not listed in UFILES!

help?

Thanks!
Steve

--
Steve Wampler -- swamp...@noao.edu
The gods that smiled on your birth are now laughing out loud.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group

Re: [Unicon-group] Svn Update

[Steve Wampler]

On 06/15/2017 11:38 PM, Jafar Al-Gharaibeh wrote:
> Status Update:
>
>While not done yet but the progress that has been made so far is enough to 
allow people to give the new changes a
> try. Basically, what we are trying to do is move a way from any "manual" 
configuration where end users don't have to
> edit files to define this or enable that to control whether a particular 
feature is enabled or not.  We are also leaving
> no chance of guessing on the end user part to get the correct configuration 
for an underlying platform. The
> configuration script should be able to figure it out on its own in the vast 
majority of cases. We will update the
> documentation on the website in the next few days on how to build or 
configure Unicon moving forward. The instructions
> are easy, checkout the sources and just do:
>
> ./configure && make
>
> And  that is all you need (crossing fingers).

On my Linux/CentOS 7 system, I had a few problems:

'make Pure' - no issues.

svn update - kept failing because it would find unversioned Makefiles
   and an occassional unversioned directory.  Kept removing those and
   rerunning the update until no more failures.

./configure && make - failed the first time on the make.  It
   printed out the old help message:
   ---
   UNIX: Run "make Configure name=system" or "make X-Configure name=system" or "make 
build name=system"
  where system is one of those in config/unix.
   Windows (MSVC): Run "nmake NT-Configure" or "nmake W-Configure".
   Windows (GCC): Run "make NT-Configure-GCC" or "make W-Configure-GCC".
   Windows (both): Then add the Unicon bin directory to your path.
   All: after configuration, run "make (or nmake) Unicon".
   ---
   A quick showed that the main Makefile hadn't been updated.
   Removed it, did an svn update on it and reran command.

./configure && make - (#2) no problems building icont, iconc, and unicon,
   and most of the *.icn code through compiling webup.icn.  Then:
   ---
   make[3]: *** No rule to make target `event.u', needed by `all'.  Stop.
   make[3]: Leaving directory `/disk/opt/svn/unicon/unicon/uni/lib'
   make[2]: *** [lib] Error 2
   make[2]: Leaving directory `/disk/opt/svn/unicon/unicon/uni'
   make[1]: *** [Unicon] Error 2
   make[1]: Leaving directory `/disk/opt/svn/unicon/unicon'
   make: *** [default] Error 2
   -
   There is a file 'event.u' in ipl/lib, but I can't figure out
   why Makefile in uni/lib thinks event.u needs to be built as
   it's not listed in UFILES!

help?

Thanks!
Steve

--
Steve Wampler -- swamp...@noao.edu
The gods that smiled on your birth are now laughing out loud.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group

Re: [Unicon-group] Svn Update

[Jafar Al-Gharaibeh]

SVN Update 2:

It is probably safe now to proceed and update if you have been holding
off. Again, make sure to "make Pure" first. Since some files got deleted,
some files were added, and some files that were being copied from/to
various places are now checked in. If after updating you get build error I
would try doing a fresh svn checkout and see how it goes before trying
anything else.

Windows hasn't been worked yet. It is on my list of things to do this week.

Sorry for any inconvenience,
Jafar

On Fri, Jun 16, 2017 at 1:38 AM, Jafar Al-Gharaibeh 
wrote:

> Status Update:
>
>   While not done yet but the progress that has been made so far is enough
> to allow people to give the new changes a try. Basically, what we are
> trying to do is move a way from any "manual" configuration where end users
> don't have to edit files to define this or enable that to control whether a
> particular feature is enabled or not.  We are also leaving no chance of
> guessing on the end user part to get the correct configuration for an
> underlying platform. The configuration script should be able to figure it
> out on its own in the vast majority of cases. We will update the
> documentation on the website in the next few days on how to build or
> configure Unicon moving forward. The instructions are easy, checkout the
> sources and just do:
>
> ./configure && make
>
> And  that is all you need (crossing fingers).
>
> You only need to call ./configure the first time you build and after a
> "make Pure" which resets everything. Make sure to call make Pure if you
> need  fresh start or if their are major updates including to the build
> system itself.
>
> ./configure --help tells you everything you need to know, most features
> can be turn off by --disable-FEATURE
>
> for example ./configure --disable-concurrency will allow you to build
> without concurrent threads. By default all features are turned on as long
> as the dependencies are met. You can also disable a particular linked
> library. For Example, assume you want graphics but don't want JPG support
> for some reason (you want a smaller iconx maybe)  then you can do:
>
> ./configure --without-jpg
>
> in summary, --disable is a feature level control while --without is a
> library level control. Of course some of these libraries might be
> dependencies for a feature, for example, on Linux, doing --without-xlib
> will end up having the same effect as  --disable-graphics. It is
> recommended to control things at the features level unless you want a finer
> granularity control for some reason. Don't forget:
>
> ./configure --help
>
> The changes have been tested on a few systems so let us know how it goes
> on your particular platform. This work has not been made compatible with
> Windows yet, but it is  on the road map.
>
> Happy configuration, and most importantly, Happy Unicon coding!
>
> Cheers,
> The Unicon Team
>
>
>
> On Tue, Jun 13, 2017 at 10:09 PM, Jafar Al-Gharaibeh 
> wrote:
>
>> Greetings Fellow Uniconers,
>>
>>I committed changes to svn today and I will make more changes over the
>> next few days that affect the configuration and the build system of Unicon.
>> I would like to bring up two points to your attention:
>>
>>1- If you are on a production system my advice is to refrain form
>> updating until the dust settles just in case something goes wrong. I expect
>> this to not take more than a few days. I didn't see any issues yet. Please
>> let me know if you have any troubles and I will fix as soon as possible.
>>
>> 2- If you decide to update, make sure to start "clean" by doing:
>>
>>   make Pure
>>
>> at the top level before updating. Files/configurations are being shuffled
>> around and new ones are introduced, having local changes will most likely
>> create trouble! you have been warned! :-)
>>
>> Sit tight and enjoy the ride!
>>
>> Cheers,
>> Jafar
>>
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group

Re: [Unicon-group] Svn Update

[Jafar Al-Gharaibeh]

Sergey,

   As I mentioned in the original email, this doesn't work on Windows yet.
I'm leaving Window until the end as it has its own build system. That
should continue to work as-is.

Thank you for the report. The output gave me some clues already on what to
expect on windows, and it looks promising. I will update you When Windows
is ready for this.

--Jafar

On Fri, Jun 16, 2017 at 3:56 AM, Sergey Logichev 
wrote:

> Great job! Thank you, Jafar!
> But when I tried to build the new unicon (after I updated from SVN) on
> Windows 10 it failed.
> See my output attached.
>
> Sincerely,
> Sergey
>
> 16.06.2017, 09:39, "Jafar Al-Gharaibeh" :
>
> Status Update:
>
>   While not done yet but the progress that has been made so far is enough
> to allow people to give the new changes a try. Basically, what we are
> trying to do is move a way from any "manual" configuration where end users
> don't have to edit files to define this or enable that to control whether a
> particular feature is enabled or not.  We are also leaving no chance of
> guessing on the end user part to get the correct configuration for an
> underlying platform. The configuration script should be able to figure it
> out on its own in the vast majority of cases. We will update the
> documentation on the website in the next few days on how to build or
> configure Unicon moving forward. The instructions are easy, checkout the
> sources and just do:
>
> ./configure && make
>
> And  that is all you need (crossing fingers).
>
> You only need to call ./configure the first time you build and after a
> "make Pure" which resets everything. Make sure to call make Pure if you
> need  fresh start or if their are major updates including to the build
> system itself.
>
> ./configure --help tells you everything you need to know, most features
> can be turn off by --disable-FEATURE
>
> for example ./configure --disable-concurrency will allow you to build
> without concurrent threads. By default all features are turned on as long
> as the dependencies are met. You can also disable a particular linked
> library. For Example, assume you want graphics but don't want JPG support
> for some reason (you want a smaller iconx maybe)  then you can do:
>
> ./configure --without-jpg
>
> in summary, --disable is a feature level control while --without is a
> library level control. Of course some of these libraries might be
> dependencies for a feature, for example, on Linux, doing --without-xlib
> will end up having the same effect as  --disable-graphics. It is
> recommended to control things at the features level unless you want a finer
> granularity control for some reason. Don't forget:
>
> ./configure --help
>
> The changes have been tested on a few systems so let us know how it goes
> on your particular platform. This work has not been made compatible with
> Windows yet, but it is  on the road map.
>
> Happy configuration, and most importantly, Happy Unicon coding!
>
> Cheers,
> The Unicon Team
>
>
>
> On Tue, Jun 13, 2017 at 10:09 PM, Jafar Al-Gharaibeh 
> wrote:
>
> Greetings Fellow Uniconers,
>
>I committed changes to svn today and I will make more changes over the
> next few days that affect the configuration and the build system of Unicon.
> I would like to bring up two points to your attention:
>
>1- If you are on a production system my advice is to refrain form
> updating until the dust settles just in case something goes wrong. I expect
> this to not take more than a few days. I didn't see any issues yet. Please
> let me know if you have any troubles and I will fix as soon as possible.
>
> 2- If you decide to update, make sure to start "clean" by doing:
>
>   make Pure
>
> at the top level before updating. Files/configurations are being shuffled
> around and new ones are introduced, having local changes will most likely
> create trouble! you have been warned! :-)
>
> Sit tight and enjoy the ride!
>
> Cheers,
> Jafar
>
> ,
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ,
>
> ___
> Unicon-group mailing list
> Unicon-group@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/unicon-group
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group

Re: [Unicon-group] Svn Update

[Sergey Logichev]

Great job! Thank you, Jafar!But when I tried to build the new unicon (after I updated from SVN) on Windows 10 it failed.See my output attached. Sincerely,Sergey 16.06.2017, 09:39, "Jafar Al-Gharaibeh" :Status Update:   While not done yet but the progress that has been made so far is enough to allow people to give the new changes a try. Basically, what we are trying to do is move a way from any "manual" configuration where end users don't have to edit files to define this or enable that to control whether a particular feature is enabled or not.  We are also leaving no chance of guessing on the end user part to get the correct configuration for an underlying platform. The configuration script should be able to figure it out on its own in the vast majority of cases. We will update the documentation on the website in the next few days on how to build or configure Unicon moving forward. The instructions are easy, checkout the sources and just do: ./configure && make And  that is all you need (crossing fingers). You only need to call ./configure the first time you build and after a "make Pure" which resets everything. Make sure to call make Pure if you need  fresh start or if their are major updates including to the build system itself.  ./configure --help tells you everything you need to know, most features can be turn off by --disable-FEATURE for example ./configure --disable-concurrency will allow you to build without concurrent threads. By default all features are turned on as long as the dependencies are met. You can also disable a particular linked library. For Example, assume you want graphics but don't want JPG support for some reason (you want a smaller iconx maybe)  then you can do: ./configure --without-jpg in summary, --disable is a feature level control while --without is a library level control. Of course some of these libraries might be dependencies for a feature, for example, on Linux, doing --without-xlib will end up having the same effect as  --disable-graphics. It is recommended to control things at the features level unless you want a finer granularity control for some reason. Don't forget: ./configure --help The changes have been tested on a few systems so let us know how it goes on your particular platform. This work has not been made compatible with Windows yet, but it is  on the road map.   Happy configuration, and most importantly, Happy Unicon coding! Cheers,The Unicon TeamOn Tue, Jun 13, 2017 at 10:09 PM, Jafar Al-Gharaibeh  wrote:Greetings Fellow Uniconers,    I committed changes to svn today and I will make more changes over the next few days that affect the configuration and the build system of Unicon. I would like to bring up two points to your attention:    1- If you are on a production system my advice is to refrain form updating until the dust settles just in case something goes wrong. I expect this to not take more than a few days. I didn't see any issues yet. Please let me know if you have any troubles and I will fix as soon as possible.  2- If you decide to update, make sure to start "clean" by doing:   make Pure  at the top level before updating. Files/configurations are being shuffled around and new ones are introduced, having local changes will most likely create trouble! you have been warned! :-)  Sit tight and enjoy the ride! Cheers,Jafar ,--Check out the vibrant tech community on one of the world's mostengaging tech sites, Slashdot.org! http://sdm.link/slashdot,___Unicon-group mailing listUnicon-group@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/unicon-groupc:\work\unicon>sh configure
checking build system type... i686-pc-mingw32
checking host system type... i686-pc-mingw32
##
Configuring Unicon Host: i686_
##
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.exe
checking for suffix of executables... .exe
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__..

Re: [Unicon-group] Svn Update

[Sergey Logichev]

Jafar,My respect!Are you still in the process? I am impatient to try the new update.Will it include iconc fixed for Windows? Please let know when you finish. Sincerely,Sergey 16.06.2017, 09:58, "Jafar Al-Gharaibeh" :Bruce, You can see the available options  under --help. OVLD is not added yet. I will add it in a day or two and it will be turned off by default.  Thanks for bringing that to my attention. --Jafar On Jun 16, 2017 1:54 AM, "Bruce & Breeanna Rennie"  wrote:Good evening Jafar,Does that mean, OVLD is also configured, or is this a manual thing I still need to do?regardsBruce RennieOn 16/06/17 16:38, Jafar Al-Gharaibeh wrote:Status Update:  While not done yet but the progress that has been made so far is enough to allow people to give the new changes a try. Basically, what we are trying to do is move a way from any "manual" configuration where end users don't have to edit files to define this or enable that to control whether a particular feature is enabled or not.  We are also leaving no chance of guessing on the end user part to get the correct configuration for an underlying platform. The configuration script should be able to figure it out on its own in the vast majority of cases. We will update the documentation on the website in the next few days on how to build or configure Unicon moving forward. The instructions are easy, checkout the sources and just do:./configure && makeAnd  that is all you need (crossing fingers).You only need to call ./configure the first time you build and after a "make Pure" which resets everything. Make sure to call make Pure if you need  fresh start or if their are major updates including to the build system itself../configure --help tells you everything you need to know, most features can be turn off by --disable-FEATUREfor example ./configure --disable-concurrency will allow you to build without concurrent threads. By default all features are turned on as long as the dependencies are met. You can also disable a particular linked library. For Example, assume you want graphics but don't want JPG support for some reason (you want a smaller iconx maybe)  then you can do:./configure --without-jpgin summary, --disable is a feature level control while --without is a library level control. Of course some of these libraries might be dependencies for a feature, for example, on Linux, doing --without-xlib will end up having the same effect as  --disable-graphics. It is recommended to control things at the features level unless you want a finer granularity control for some reason. Don't forget:./configure --helpThe changes have been tested on a few systems so let us know how it goes on your particular platform. This work has not been made compatible with Windows yet, but it is  on the road map.Happy configuration, and most importantly, Happy Unicon coding!Cheers,The Unicon TeamOn Tue, Jun 13, 2017 at 10:09 PM, Jafar Al-Gharaibeh > wrote:    Greetings Fellow Uniconers,       I committed changes to svn today and I will make more changes    over the next few days that affect the configuration and the build    system of Unicon. I would like to bring up two points to your    attention:       1- If you are on a production system my advice is to refrain    form updating until the dust settles just in case something goes    wrong. I expect this to not take more than a few days. I didn't    see any issues yet. Please let me know if you have any troubles    and I will fix as soon as possible.    2- If you decide to update, make sure to start "clean" by doing:      make Pure    at the top level before updating. Files/configurations are being    shuffled around and new ones are introduced, having local changes    will most likely create trouble! you have been warned! :-)    Sit tight and enjoy the ride!    Cheers,    Jafar--Check out the vibrant tech community on one of the world's mostengaging tech sites, Slashdot.org! http://sdm.link/slashdot___Unicon-group mailing listUnicon-group@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/unicon-group--Check out the vibrant tech community on one of the world's mostengaging tech sites, Slashdot.org! http://sdm.link/slashdot___Unicon-group mailing listUnicon-group@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/unicon-group,--Check out the vibrant tech community on one of the world's mostengaging tech sites, Slashdot.org! http://sdm.link/slashdot,___Unicon-group mailing listUnicon-group@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/unicon-group-

Re: [Unicon-group] Svn Update

[Jafar Al-Gharaibeh]

Bruce,

You can see the available options  under --help. OVLD is not added yet. I
will add it in a day or two and it will be turned off by default.

Thanks for bringing that to my attention.

--Jafar

On Jun 16, 2017 1:54 AM, "Bruce & Breeanna Rennie" 
wrote:

> Good evening Jafar,
>
> Does that mean, OVLD is also configured, or is this a manual thing I still
> need to do?
>
> regards
>
> Bruce Rennie
>
> On 16/06/17 16:38, Jafar Al-Gharaibeh wrote:
>
>> Status Update:
>>
>>   While not done yet but the progress that has been made so far is enough
>> to allow people to give the new changes a try. Basically, what we are
>> trying to do is move a way from any "manual" configuration where end users
>> don't have to edit files to define this or enable that to control whether a
>> particular feature is enabled or not.  We are also leaving no chance of
>> guessing on the end user part to get the correct configuration for an
>> underlying platform. The configuration script should be able to figure it
>> out on its own in the vast majority of cases. We will update the
>> documentation on the website in the next few days on how to build or
>> configure Unicon moving forward. The instructions are easy, checkout the
>> sources and just do:
>>
>> ./configure && make
>>
>> And  that is all you need (crossing fingers).
>>
>> You only need to call ./configure the first time you build and after a
>> "make Pure" which resets everything. Make sure to call make Pure if you
>> need  fresh start or if their are major updates including to the build
>> system itself.
>>
>> ./configure --help tells you everything you need to know, most features
>> can be turn off by --disable-FEATURE
>>
>> for example ./configure --disable-concurrency will allow you to build
>> without concurrent threads. By default all features are turned on as long
>> as the dependencies are met. You can also disable a particular linked
>> library. For Example, assume you want graphics but don't want JPG support
>> for some reason (you want a smaller iconx maybe)  then you can do:
>>
>> ./configure --without-jpg
>>
>> in summary, --disable is a feature level control while --without is a
>> library level control. Of course some of these libraries might be
>> dependencies for a feature, for example, on Linux, doing --without-xlib
>> will end up having the same effect as  --disable-graphics. It is
>> recommended to control things at the features level unless you want a finer
>> granularity control for some reason. Don't forget:
>>
>> ./configure --help
>>
>> The changes have been tested on a few systems so let us know how it goes
>> on your particular platform. This work has not been made compatible with
>> Windows yet, but it is  on the road map.
>> Happy configuration, and most importantly, Happy Unicon coding!
>>
>> Cheers,
>> The Unicon Team
>>
>>
>>
>> On Tue, Jun 13, 2017 at 10:09 PM, Jafar Al-Gharaibeh > > wrote:
>>
>> Greetings Fellow Uniconers,
>>
>>I committed changes to svn today and I will make more changes
>> over the next few days that affect the configuration and the build
>> system of Unicon. I would like to bring up two points to your
>> attention:
>>
>>1- If you are on a production system my advice is to refrain
>> form updating until the dust settles just in case something goes
>> wrong. I expect this to not take more than a few days. I didn't
>> see any issues yet. Please let me know if you have any troubles
>> and I will fix as soon as possible.
>>
>> 2- If you decide to update, make sure to start "clean" by doing:
>>
>>   make Pure
>>
>> at the top level before updating. Files/configurations are being
>> shuffled around and new ones are introduced, having local changes
>> will most likely create trouble! you have been warned! :-)
>>
>> Sit tight and enjoy the ride!
>>
>> Cheers,
>> Jafar
>>
>>
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>> ___
>> Unicon-group mailing list
>> Unicon-group@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/unicon-group
>>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Unicon-group mailing list
> Unicon-group@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/unicon-group
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Unicon-grou

Re: [Unicon-group] Svn Update

[Bruce & Breeanna Rennie]

Good evening Jafar,

Does that mean, OVLD is also configured, or is this a manual thing I 
still need to do?


regards

Bruce Rennie

On 16/06/17 16:38, Jafar Al-Gharaibeh wrote:

Status Update:

  While not done yet but the progress that has been made so far is 
enough to allow people to give the new changes a try. Basically, what 
we are trying to do is move a way from any "manual" configuration 
where end users don't have to edit files to define this or enable that 
to control whether a particular feature is enabled or not.  We are 
also leaving no chance of guessing on the end user part to get the 
correct configuration for an underlying platform. The configuration 
script should be able to figure it out on its own in the vast majority 
of cases. We will update the documentation on the website in the next 
few days on how to build or configure Unicon moving forward. The 
instructions are easy, checkout the sources and just do:


./configure && make

And  that is all you need (crossing fingers).

You only need to call ./configure the first time you build and after a 
"make Pure" which resets everything. Make sure to call make Pure if 
you need  fresh start or if their are major updates including to the 
build system itself.


./configure --help tells you everything you need to know, most 
features can be turn off by --disable-FEATURE


for example ./configure --disable-concurrency will allow you to build 
without concurrent threads. By default all features are turned on as 
long as the dependencies are met. You can also disable a particular 
linked library. For Example, assume you want graphics but don't want 
JPG support for some reason (you want a smaller iconx maybe)  then you 
can do:


./configure --without-jpg

in summary, --disable is a feature level control while --without is a 
library level control. Of course some of these libraries might be 
dependencies for a feature, for example, on Linux, doing 
--without-xlib will end up having the same effect as 
 --disable-graphics. It is recommended to control things at the 
features level unless you want a finer granularity control for some 
reason. Don't forget:


./configure --help

The changes have been tested on a few systems so let us know how it 
goes on your particular platform. This work has not been made 
compatible with Windows yet, but it is  on the road map.

Happy configuration, and most importantly, Happy Unicon coding!

Cheers,
The Unicon Team



On Tue, Jun 13, 2017 at 10:09 PM, Jafar Al-Gharaibeh 
mailto:to.ja...@gmail.com>> wrote:


Greetings Fellow Uniconers,

   I committed changes to svn today and I will make more changes
over the next few days that affect the configuration and the build
system of Unicon. I would like to bring up two points to your
attention:

   1- If you are on a production system my advice is to refrain
form updating until the dust settles just in case something goes
wrong. I expect this to not take more than a few days. I didn't
see any issues yet. Please let me know if you have any troubles
and I will fix as soon as possible.

2- If you decide to update, make sure to start "clean" by doing:

  make Pure

at the top level before updating. Files/configurations are being
shuffled around and new ones are introduced, having local changes
will most likely create trouble! you have been warned! :-)

Sit tight and enjoy the ride!

Cheers,
Jafar




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


___
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group

Re: [Unicon-group] Svn Update

[Jafar Al-Gharaibeh]

Status Update:

  While not done yet but the progress that has been made so far is enough
to allow people to give the new changes a try. Basically, what we are
trying to do is move a way from any "manual" configuration where end users
don't have to edit files to define this or enable that to control whether a
particular feature is enabled or not.  We are also leaving no chance of
guessing on the end user part to get the correct configuration for an
underlying platform. The configuration script should be able to figure it
out on its own in the vast majority of cases. We will update the
documentation on the website in the next few days on how to build or
configure Unicon moving forward. The instructions are easy, checkout the
sources and just do:

./configure && make

And  that is all you need (crossing fingers).

You only need to call ./configure the first time you build and after a
"make Pure" which resets everything. Make sure to call make Pure if you
need  fresh start or if their are major updates including to the build
system itself.

./configure --help tells you everything you need to know, most features can
be turn off by --disable-FEATURE

for example ./configure --disable-concurrency will allow you to build
without concurrent threads. By default all features are turned on as long
as the dependencies are met. You can also disable a particular linked
library. For Example, assume you want graphics but don't want JPG support
for some reason (you want a smaller iconx maybe)  then you can do:

./configure --without-jpg

in summary, --disable is a feature level control while --without is a
library level control. Of course some of these libraries might be
dependencies for a feature, for example, on Linux, doing --without-xlib
will end up having the same effect as  --disable-graphics. It is
recommended to control things at the features level unless you want a finer
granularity control for some reason. Don't forget:

./configure --help

The changes have been tested on a few systems so let us know how it goes on
your particular platform. This work has not been made compatible with
Windows yet, but it is  on the road map.

Happy configuration, and most importantly, Happy Unicon coding!

Cheers,
The Unicon Team



On Tue, Jun 13, 2017 at 10:09 PM, Jafar Al-Gharaibeh 
wrote:

> Greetings Fellow Uniconers,
>
>I committed changes to svn today and I will make more changes over the
> next few days that affect the configuration and the build system of Unicon.
> I would like to bring up two points to your attention:
>
>1- If you are on a production system my advice is to refrain form
> updating until the dust settles just in case something goes wrong. I expect
> this to not take more than a few days. I didn't see any issues yet. Please
> let me know if you have any troubles and I will fix as soon as possible.
>
> 2- If you decide to update, make sure to start "clean" by doing:
>
>   make Pure
>
> at the top level before updating. Files/configurations are being shuffled
> around and new ones are introduced, having local changes will most likely
> create trouble! you have been warned! :-)
>
> Sit tight and enjoy the ride!
>
> Cheers,
> Jafar
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group